From: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
---|---|
To: | Craig Ringer <craig(at)postnewspapers(dot)com(dot)au> |
Cc: | PG-General Mailing List <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Cheapest way to poll for notifications? |
Date: | 2009-12-10 15:48:24 |
Message-ID: | b42b73150912100748r2f3a3fcelb4ea9e43f9e0f0b7@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-jdbc |
On Thu, Dec 10, 2009 at 8:23 AM, Craig Ringer
<craig(at)postnewspapers(dot)com(dot)au> 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.
merlin
From | Date | Subject | |
---|---|---|---|
Next Message | Craig Ringer | 2009-12-10 16:10:06 | Re: Cheapest way to poll for notifications? |
Previous Message | CG | 2009-12-10 15:27:54 | Re: pg_dump and ON DELETE CASCADE problem |
From | Date | Subject | |
---|---|---|---|
Next Message | Craig Ringer | 2009-12-10 16:10:06 | Re: Cheapest way to poll for notifications? |
Previous Message | Tom Lane | 2009-12-10 15:11:04 | Re: Cheapest way to poll for notifications? |