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


From: Neil Conway <neilc(at)samurai(dot)com>
To: Marko Kreen <markokr(at)gmail(dot)com>
Cc: PGSQL-Patches <pgsql-patches(at)postgresql(dot)org>
Subject: Re: RESET SESSION v3
Date: 2007-04-12 06:57:42
Message-ID: 1176361062.6593.14.camel@localhost.localdomain (view raw, whole thread or download thread mbox)
Lists: pgsql-patches
On Sun, 2007-04-08 at 11:08 +0300, Marko Kreen wrote:
> I think implicit ABORT would annoy various tools that
> partially parse user sql and expect to know what transaction
> state currently is.  For them a new tranaction control statement
> would be nuisance.

That's not the only alternative: we could also either disallow all of
the "ALL" variants in a transaction block, or allow RESET SESSION inside
a transaction block.

I've committed the patch basically as-is: thanks for the patch. I don't
feel strongly about the above, but if there's a consensus, we can change
the behavior later.


In response to


pgsql-patches by date

Next:From: Heikki LinnakangasDate: 2007-04-12 08:40:19
Subject: Re: [HACKERS] Fix mdsync never-ending loop problem
Previous:From: Jeff FrostDate: 2007-04-12 05:33:12
Subject: Re: Slow Postgresql server

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