Re: dropdb/contrib-regression

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Neil Conway <neilc(at)samurai(dot)com>
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:44:11
Message-ID: 9258.1102995851@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

Neil Conway <neilc(at)samurai(dot)com> writes:
> 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,

> 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() ?

If it's optional, then to make it useful for the problem at hand, we'd
have to expose the option clear up to the psql command line, which seems
like a lotta work.

At the moment I think a "sleep" in the contrib makefile is sufficient
(though note I intended to apply it only to installcheck not the other
actions ;-))

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2004-12-14 06:54:47 Re: dropdb/contrib-regression
Previous Message Neil Conway 2004-12-14 03:39:49 Re: dropdb/contrib-regression

Browse pgsql-patches by date

  From Date Subject
Next Message Andrew Dunstan 2004-12-14 06:54:47 Re: dropdb/contrib-regression
Previous Message Neil Conway 2004-12-14 03:39:49 Re: dropdb/contrib-regression