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

pgpool and ABORT

From: Thomas F(dot)O'Connell <tfo(at)sitening(dot)com>
To: PgSQL Admin <pgsql-admin(at)postgresql(dot)org>
Subject: pgpool and ABORT
Date: 2005-03-20 23:35:49
Message-ID: 0860bc19e1b883911bb20df78d6e26b9@sitening.com (view raw or flat)
Thread:
Lists: pgsql-admin
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:

http://archives.postgresql.org/pgsql-general/2004-04/msg01154.php

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.

-tfo

--
Thomas F. O'Connell
Co-Founder, Information Architect
Sitening, LLC
http://www.sitening.com/
110 30th Avenue North, Suite 6
Nashville, TN 37203-6320
615-260-0005


pgsql-admin by date

Next:From: Tom LaneDate: 2005-03-21 02:57:36
Subject: Re: pg_dump problem.
Previous:From: Mont RothsteinDate: 2005-03-20 18:02:52
Subject: Re: Multiple languages in one database

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