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

Re: NOTICE: BeginTransactionBlock and not in default

From: Michael Meskes <meskes(at)postgresql(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: ganesan <ganesanm(at)technauts(dot)com>, pgsql-interfaces(at)postgresql(dot)org
Subject: Re: NOTICE: BeginTransactionBlock and not in default
Date: 2000-05-02 09:24:07
Message-ID: 20000502112407.B3097@fam-meskes.de (view raw or flat)
Thread:
Lists: pgsql-interfaces
On Sat, Apr 22, 2000 at 07:15:14PM -0400, Tom Lane wrote:
> > I could open database connection in the parent process and
> > pass it on to all the children.
> 
> Wrong ... you'll have to make each child open its own connection.
> There's no provision in the backend for dealing with concurrent
> queries coming through the same socket.  I'm surprised it didn't
> crash even more spectacularly than you describe...

That's because the queries didn't make it to the backend at all. libecpg
does not know which connection to send the query to and thus gives this
error message.

Michael
-- 
Michael Meskes                         | Go SF 49ers!
Th.-Heuss-Str. 61, D-41812 Erkelenz    | Go Rhein Fire!
Tel.: (+49) 2431/72651                 | Use Debian GNU/Linux!
Email: Michael(at)Fam-Meskes(dot)De           | Use PostgreSQL!

pgsql-interfaces by date

Next:From: Bruce MomjianDate: 2000-05-02 10:55:47
Subject: Re: Request for 7.0 JDBC status
Previous:From: Michael MeskesDate: 2000-05-02 09:23:12
Subject: Re: ECPG and WHENEVER statements

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