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

Re: Connection Pooling, a year later

From: Lincoln Yeoh <lyeoh(at)pop(dot)jaring(dot)my>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>
Cc: mlw <markw(at)mohawksoft(dot)com>, owensmk(at)earthlink(dot)net, pgsql-hackers(at)postgresql(dot)org, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: Connection Pooling, a year later
Date: 2001-12-18 11:02:02
Message-ID: 3.0.5.32.20011218190202.0086db00@192.228.128.13 (view raw or flat)
Thread:
Lists: pgsql-hackers
At 11:49 PM 12/17/01 -0500, Bruce Momjian wrote:
>new person.  Now, if you want to abort a left-over transaction, you can
>do an ABORT but that is going to show up in the server logs because an
>ABORT without a transaction causes an error message.

I do a lot of rollbacks typically. Would that cause errors?

I prefer doing rollbacks to commits when in doubt.

Regards,
Link.



In response to

Responses

pgsql-hackers by date

Next:From: Lincoln YeohDate: 2001-12-18 11:14:51
Subject: Re: Connection Pooling, a year later
Previous:From: Jussi MikkolaDate: 2001-12-18 10:54:13
Subject: Re: 7.2 is slow?

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