I'm using pgpool in a fairly high-traffic environment, and I regularly
get this warning from pgpool calling ABORT:
WARNING: there is no transaction in progress
I found this post in the archives:
But the README for pgpool asserts:
Note that "ABORT" will not be issued if the backend is 7.4 or later
and the session is not in a transaction block.
I'm just curious why I'm still seeing the ABORTs if these sessions are
not in a transaction block.
I'm running postgres 7.4.6 and pgpool 2.5.1.
Thomas F. O'Connell
Co-Founder, Information Architect
110 30th Avenue North, Suite 6
Nashville, TN 37203-6320
pgsql-admin by date
|Next:||From: Tom Lane||Date: 2005-03-21 02:57:36|
|Subject: Re: pg_dump problem. |
|Previous:||From: Mont Rothstein||Date: 2005-03-20 18:02:52|
|Subject: Re: Multiple languages in one database|