Re: SELECT ... FOR UPDATE and ResultSet - Mailing list pgsql-jdbc

From Tom Lane
Subject Re: SELECT ... FOR UPDATE and ResultSet
Date
Msg-id 2427.1073009537@sss.pgh.pa.us
Whole thread Raw
In response to SELECT ... FOR UPDATE and ResultSet  (Jeffrey Tenny <jeffrey.tenny@comcast.net>)
Responses Re: SELECT ... FOR UPDATE and ResultSet  (Jeffrey Tenny <jeffrey.tenny@comcast.net>)
Re: SELECT ... FOR UPDATE and ResultSet  (Barry Lind <blind@xythos.com>)
List pgsql-jdbc
Jeffrey Tenny <jeffrey.tenny@comcast.net> writes:
> Can I count on this behavior for PostgreSQL?  Or will it fail to lock
> all rows if
> I have a sufficiently large ResultSet and Connection.setFetchSize() does
> it's magic?

In the current implementation, the backend will only lock those rows
actually returned to the client.  If setFetchSize() causes not all the
rows to be fetched, you lose ...

            regards, tom lane

pgsql-jdbc by date:

Previous
From: Jeffrey Tenny
Date:
Subject: SELECT ... FOR UPDATE and ResultSet
Next
From: Tom Lane
Date:
Subject: Re: PostgreSQL design question