| From: | Greg Stark <gsstark(at)mit(dot)edu> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>, Jasen Betts <jasen(at)xnet(dot)co(dot)nz>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Clients disconnect but query still runs |
| Date: | 2009-07-30 14:30:15 |
| Message-ID: | 407d949e0907300730m7d78783kf9e448d1468fc440@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, Jul 30, 2009 at 3:20 PM, Tom Lane<tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> The earlier part of the discussion was focused on getting the kernel
> to actively tell us when the connection had dropped. That would be
> workable if we found a way to request it, but I think we'd run out of
> options :-(
Yeah, everything I've found on SIGIO indicates it would fire whenever
the socket was readable which isn't what we want. Does anyone have a
pointer for a full documentation on how to use it?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2009-07-30 14:33:42 | Re: PostgreSQL server listen on other port than 5432 |
| Previous Message | Josh Kupershmidt | 2009-07-30 14:25:25 | Re: PG equivalent of "mysqlhotcopy"? |