Re: Slow response of PostgreSQL

From: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>
To: "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(dot)com>
Cc: Bill Moran <wmoran(at)potentialtech(dot)com>, Saleem Burhani Baloch <peseek(at)khi(dot)wol(dot)net(dot)pk>, pgsql-performance(at)postgresql(dot)org
Subject: Re: Slow response of PostgreSQL
Date: 2004-02-18 04:52:55
Message-ID: 4032EFA7.2040106@familyhealth.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

>>>How about SELECT ... FOR UPDATE?
>>
>>No, because users cannot read the locked row in that case.
>
>
> I just tested it (within transactions) and it appeared that I could still
> view the rows selected for update.

Ah, true. My mistake. OK, well you can do it in postgres then...

Chris

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Kevin Brown 2004-02-18 06:52:26 Re: UPDATE with subquery too slow
Previous Message Bill Moran 2004-02-18 02:21:31 Re: Slow response of PostgreSQL