On 1/25/07, Weslee Bilodeau <[EMAIL PROTECTED]> wrote:
Where I work I'm in charge of more then a few PostgreSQL databases.
I understand why idle in transaction is bad, however I have some
developers who I'm having a real difficult time fully explaining to them
why its bad.
Oh, and by bad I mean
Well, in very short terms: a "idle" transaction is not committed. This means,
when it's a writing transaction, that in the best case you have one or more
row locks blocking access to the updated/inserted rows and in the worst case
one or more table locks, which will block access to a table compl
On Wed, Jan 24, 2007 at 01:15:43PM -0800, Weslee Bilodeau wrote:
> Where I work I'm in charge of more then a few PostgreSQL databases.
>
> I understand why idle in transaction is bad, however I have some
> developers who I'm having a real difficult time fully explaining to them
> why its bad.
It'
Where I work I'm in charge of more then a few PostgreSQL databases.
I understand why idle in transaction is bad, however I have some
developers who I'm having a real difficult time fully explaining to them
why its bad.
Oh, and by bad I mean they have transactions that are sitting idle for
6+ hour
