Re: SELECT ... FOR UPDATE and ResultSet

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Jeffrey Tenny <jeffrey(dot)tenny(at)comcast(dot)net>
Cc: postgres jdbc <pgsql-jdbc(at)postgresql(dot)org>
Subject: Re: SELECT ... FOR UPDATE and ResultSet
Date: 2004-01-02 02:12:17
Message-ID: 2427.1073009537@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

Jeffrey Tenny <jeffrey(dot)tenny(at)comcast(dot)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

In response to

Responses

Browse pgsql-jdbc by date

  From Date Subject
Next Message Tom Lane 2004-01-02 03:04:58 Re: PostgreSQL design question
Previous Message Jeffrey Tenny 2004-01-02 01:26:49 SELECT ... FOR UPDATE and ResultSet