| From: | Neil Conway <neilc(at)samurai(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: dropdb/contrib-regression |
| Date: | 2004-12-14 03:39:49 |
| Message-ID: | 1102995589.28882.12.camel@localhost.localdomain |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
On Mon, 2004-12-13 at 19:29 -0500, Tom Lane wrote:
> A more radical solution would be to tweak libpq's PQfinish() to be a
> synchronous close, ie, wait for the backend to exit before returning.
> I think we've speculated about doing that in the past, but never been
> fully convinced that it's worth the downside of usually-unnecessary
> client delay.
I can see this being useful in some situations, but I think the current
behavior is preferable for most clients. Perhaps we could make this a
per-connection option, or supply a variant of PQfinish() ?
-Neil
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2004-12-14 03:44:11 | Re: dropdb/contrib-regression |
| Previous Message | Andrew Dunstan | 2004-12-14 01:44:53 | Re: [HACKERS] dropdb/contrib-regression |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2004-12-14 03:44:11 | Re: dropdb/contrib-regression |
| Previous Message | Neil Conway | 2004-12-14 01:59:16 | Re: pg_resetxlog as root |