Mention pgapp as a higher-level way of accessing Postgres

README.md

@@ -4,6 +4,22 @@ Asynchronous fork of [wg/epgsql](https://github.com/wg/epgsql) originally here:
 [mabrek/epgsql](https://github.com/mabrek/epgsql) and subsequently forked in order to
 provide a common fork for community development.
 
+## pgapp
+
+If you want to get up to speed quickly with code that lets you run
+Postgres queries, you might consider trying
+[epgsql/pgapp](https://github.com/epgsql/pgapp), which adds:
+
+- A 'resource pool' (currently poolboy), which lets you decide how
+  many Postgres workers you want to utilize.
+- Resilience against the database going down or other problems.  The
+  pgapp code will keep trying to reconnect to the database, but will
+  not propagate the crash up the supervisor tree, so that, for
+  instance, your web site will stay up even if the database is down
+  for some reason.  Erlang's "let it crash" is a good idea, but
+  external resources going away might not be a good reason to crash
+  your entire system.
+
 ## Motivation
 
 When you need to execute several queries, it involves a number network