Merlin Moncure wrote: > On Thu, Dec 10, 2009 at 8:23 AM, Craig Ringer > <craig@xxxxxxxxxxxxxxxxxxxxx> wrote: >> Hi >> >> As Pg doesn't presently support client push for notifications arising from >> LISTEN/NOTIFY, I'm wondering if anybody here has done any research into the >> cheapest statement to issue to check for such notifications. > > notifications are sent to the client as soon as they are generated and > the socket is not otherwise being used. psql just prints the > notifcation message following a query because that happens to be a > convenient place to do it. The only polling that has to be done (if > any) is 100% client side. There is an excellent example (in C) in the > documentation showing a method of waiting on the connection socket for > notification events when the connection is not in use by the client. Aah, that makes sense. So psql is being sent (and buffering) the notification immediately, and could choose to report it promptly - say by calling recv(...) on its socket periodically using an alarm signal. Since it's not important for psql to report notifications immediately though, it only checks after statements. Right? Anyway, thanks for the explanation, it's appreciated. -- Craig Ringer -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
