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

Re: Connection.setReadOnly()

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: John R Pierce <pierce(at)hogranch(dot)com>
Cc: Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>, Oliver Jowett <oliver(at)opencloud(dot)com>, pgsql-jdbc(at)postgresql(dot)org
Subject: Re: Connection.setReadOnly()
Date: 2009-12-11 21:38:04
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-jdbc
John R Pierce <pierce(at)hogranch(dot)com> writes:
> I've been using this...
> to detect old stale transactions and other long running operations

> in 8.4, there's a different high water mark I should be using instead?

No, the point of my comment was just that IDLE-in-transaction isn't as
dangerous as it used to be, from the perspective of whether VACUUM can
reclaim dead rows.  There are still lots of other reasons to not want
transactions sitting open without need.  They might be holding locks
for example.

			regards, tom lane

In response to

pgsql-jdbc by date

Next:From: Andreas BrandlDate: 2009-12-12 23:43:21
Subject: keeping Connection alive
Previous:From: John R PierceDate: 2009-12-11 21:24:17
Subject: Re: Connection.setReadOnly()

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