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

Re: show all;

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Marko Kreen <marko(at)l-t(dot)ee>, pgsql-patches(at)postgresql(dot)org
Subject: Re: show all;
Date: 2001-06-02 16:30:33
Message-ID: 200106021630.f52GUXA13107@candle.pha.pa.us (view raw or flat)
Thread:
Lists: pgsql-patches
> The problem is that they don't want to change the log levels.  They are
> using BEGIN;COMMIT; as an automatic thing in the PHP interface to close
> any open transaction before passing the persistent connection to another
> user.  This is a special case.

My original question has not been answered.  Is BEGIN;COMMIT; the proper
way for persistent connections to abort any transaction left open?

ABORT throws a message in the log each time if there is no open
transaction, which seems wrong for this usage.

BEGIN;COMMIT will throw an elog message if there is an open
transaction, but that is OK because it is quite rare to happen.

With this and RESET ALL, persistent connections will be safe.

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman(at)candle(dot)pha(dot)pa(dot)us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

In response to

pgsql-patches by date

Next:From: Bruce MomjianDate: 2001-06-02 16:39:41
Subject: Re: Re: AW: [HACKERS] Re: Support for %TYPE in CREATE FUNCTION
Previous:From: Jan WieckDate: 2001-06-02 16:05:22
Subject: Access statistics

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