Re: Transaction handling in extended query mode and Sync message issues

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Carlos Guzman Alvarez <carlosga(at)telefonica(dot)net>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Transaction handling in extended query mode and Sync message issues
Date: 2003-07-15 01:53:29
Message-ID: 19500.1058234009@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Carlos Guzman Alvarez <carlosga(at)telefonica(dot)net> writes:
> In the extended query mode documentation i see this:
> "Note: Sync does not cause a transaction block opened with BEGIN to be
> closed. It is possible to detect this situation since the ReadyForQuery
> message includes transaction status information."
> I have tested the same cycle with a BEGIN WORK but having the same
> problem, any idea on what i'm doing wrong ???

Did you figure this out? I can't see any way that a Sync message would
close a transaction started with BEGIN (or START TRANSACTION). It runs
the same code we run at the end of a simple-Query message, and we'd
definitely have noticed if that were causing premature commit ...

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Nikolay Kim 2003-07-15 03:25:49 Re: ERROR: MemoryContextAlloc: invalid request size
Previous Message Tom Lane 2003-07-14 23:38:35 Re: duplicate define in elog.h