Update docs about async notifications; add notice test

README.md

@@ -442,8 +442,9 @@ see `epgsql.hrl` for the record definition. `epgsql` functions may also return
 ## Server Notifications
 
 PostgreSQL may deliver two types of asynchronous message: "notices" in response
-to notice and warning messages generated by the server, and "notifications" which
-are generated by the `LISTEN/NOTIFY` mechanism.
+to [notice and warning](https://www.postgresql.org/docs/current/static/plpgsql-errors-and-messages.html)
+messages generated by the server, and [notifications](https://www.postgresql.org/docs/current/static/sql-notify.html)
+which are generated by the `LISTEN/NOTIFY` mechanism.
 
 Passing the `{async, PidOrName}` option to `epgsql:connect/3` will result in these async
 messages being sent to the specified pid or registered process, otherwise they will be dropped.

include/epgsql.hrl

@@ -15,7 +15,8 @@
 }).
 
 -record(error, {
-    severity :: fatal | error | atom(), %TODO: concretize
+    % see client_min_messages config option
+    severity :: debug | log | info | notice | warning | error | fatal | panic,
     code :: binary(),
     codename :: atom(),
     message :: binary(),

test/epgsql_tests.erl

@@ -858,6 +858,17 @@ set_notice_receiver_test(Module) ->
           {ok, undefined} = Module:set_notice_receiver(C, Self),
           EnsureNotification(<<"test2">>),
 
+          %% test PL/PgSQL NOTICE
+          {ok, [], []} = Module:squery(
+                           C, ["DO $$ BEGIN RAISE WARNING 'test notice'; END $$;"]),
+          receive
+              {epgsql, C, {notice, #error{severity = warning,
+                                          code = <<"00000">>,
+                                          message = <<"test notice">>}}} -> ok
+          after
+              100 -> erlang:error(didnt_receive_notice)
+          end,
+
           % set registered pid
           Receiver = pg_notification_receiver,
           register(Receiver, Self),