Skip site navigation (1) Skip section navigation (2)

Re: Concurrent psql patch

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Gregory Stark <stark(at)enterprisedb(dot)com>, David Fetter <david(at)fetter(dot)org>, Jim Nasby <decibel(at)decibel(dot)org>, pgsql-patches <pgsql-patches(at)postgresql(dot)org>
Subject: Re: Concurrent psql patch
Date: 2007-05-24 20:16:26
Message-ID: 20363.1180037786@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-patches
Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> Tom Lane wrote:
>> If there's more needed here, let's see an official API change,
>> not a hack.

> Well, I guess the obvious API would be something like:
>     PGAsyncStatusType PQasyncStatus(const PGconn *conn);

That would mean exposing PGAsyncStatusType, which doesn't seem like an
amazingly good idea either.  What is it that the patch actually wants
to do?

			regards, tom lane

In response to

Responses

pgsql-hackers by date

Next:From: Andrew DunstanDate: 2007-05-24 20:37:40
Subject: Re: Concurrent psql patch
Previous:From: Andrew DunstanDate: 2007-05-24 20:12:48
Subject: Re: Concurrent psql patch

pgsql-patches by date

Next:From: Andrew DunstanDate: 2007-05-24 20:37:40
Subject: Re: Concurrent psql patch
Previous:From: Andrew DunstanDate: 2007-05-24 20:12:48
Subject: Re: Concurrent psql patch

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group