[BUGS] Re: BUG #4123: Statement.setQueryTimeout does not work with Postgres Java Driver

2008-04-25 Thread Kevin Grittner
>>> On Fri, Apr 25, 2008 at 11:59 AM, in message <[EMAIL PROTECTED]>, valgog <[EMAIL PROTECTED]> wrote: > On Apr 24, 12:28 pm, [EMAIL PROTECTED] (Kris Jurka) wrote: >> On Wed, 23 Apr 2008, valgog wrote: >> > Is it possible to implement the setStatementTimeout() as somethig >> > like: >> >> > s = c

[BUGS] Re: BUG #4123: Statement.setQueryTimeout does not work with Postgres Java Driver

2008-04-25 Thread valgog
Ok, understood... that could not be so easy anyway :) I supposed that it should be something, that lays in the JDBC specs... Regards, -- Valentine On Apr 24, 12:28 pm, [EMAIL PROTECTED] (Kris Jurka) wrote: > On Wed, 23 Apr 2008, valgog wrote: > > Is it possible to implement the setStatementTimeo

Re: [BUGS] problem

2008-04-25 Thread Zdenek Kotala
The first record ctid=(0,1) is obsolete, you can delete it. It is probably race condition in VACUUM and catalog modification. Did you added or modified any user account (e.g. password change) in related time? Please, can you let us know exact version of PostgreSQL? Zdenek Kho