I have to admit I was not aware of this feature.
However, from the docs[1]:
> Commonly, the channel name is the same as the name of some table in the database, and the notify event essentially means, "I changed this table, take a look at it to see what's new".
From what I understand, you just know that something has changed, the actual change is not included in the event, so you need at least another query to see what changed.
Did I understand correctly?
In MongoDB you get the operation (insert, update, delete), the document and another few details right in the event.
[1] http://www.postgresql.org/docs/9.4/static/sql-notify.html
You can do as ddorian43 explained, by including a payload in your notification (using JSON or another format).
Or you can do as you suggested and query the database to fetch more information about the change.
Apart LISTEN/NOTIFY, which is a very powerful feature, PostgreSQL also provides "logical decoding" which solves problems similar to the ones solved by oplog tailing.
I don't know that it's story is so great. EASY, sure, but what good is easily replicating bad data?
But I don't understand that part:
> The accessible oplog was another gem that fit my project really well. Gone was the need to poll the database, I could just "watch" the oplog.
Coming from PostgreSQL, you could do the same using LISTEN/NOTIFY?