Re: [Pgpool-general] backend mismatch

From: Dave Page <dpage(at)pgadmin(dot)org>
To: Guillaume Lelarge <guillaume(at)lelarge(dot)info>
Cc: pgpool-general(at)pgfoundry(dot)org, Leonardo Carvalho <leonardotcarvalho(at)gmail(dot)com>, "Kostas P(dot)" <kostas(at)nsoft(dot)lt>, pgadmin-hackers(at)postgresql(dot)org
Subject: Re: [Pgpool-general] backend mismatch
Date: 2009-07-21 08:12:37
Message-ID: 937d27e10907210112w14c3a584nd4d2b4f3306b837c@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-hackers

On Mon, Jul 20, 2009 at 10:32 PM, Guillaume
Lelarge<guillaume(at)lelarge(dot)info> wrote:
> Le lundi 20 juillet 2009 à 19:06:50, Dave Page a écrit :
>> On Mon, Jul 20, 2009 at 5:38 PM, Guillaume
>>
>> Lelarge<guillaume(at)lelarge(dot)info> wrote:
>> > The latter. I don't see a way to catch them all easily. I'll commit this,
>> > and try to find a way to catch the others.
>>
>> Good luck with that. We use multi-sentence statements in practically
>> every SQL dialogue to group together commands like "CREATE xxx; ALTER
>> xxx; COMMENT ON xxx;" to run everything as one transaction without
>> explicitly starting or ending one. Changing that would require some
>> fairly invasive changes.
>>
>
> Hmmmm. You're right. I don't know why I didn't think about this. Should I
> revert my patch? it doesn't do any good (and no bad AFAICT).

The downside is an extra roundtrip. If it doesn't help, let's back it out.

--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com

In response to

Responses

Browse pgadmin-hackers by date

  From Date Subject
Next Message Guillaume Lelarge 2009-07-21 08:20:30 Re: Re: [pgadmin-support] pgAdmin3 Version 1.10.0 : Crash when configuring an pgAgent job
Previous Message Guillaume Lelarge 2009-07-20 21:32:46 Re: [Pgpool-general] backend mismatch