Re: Slow response of PostgreSQL

From: "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(dot)com>
To: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>
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 01:50:08
Message-ID: Pine.LNX.4.33.0402171848520.32355-100000@css120.ihs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On Wed, 18 Feb 2004, Christopher Kings-Lynne wrote:

> >>> 1- How can I lock a single record so that other users can only read
> >>> it. ??
> >>
> >>
> >> You cannot do that in PostgreSQL.
> >
> >
> > 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.

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Bill Moran 2004-02-18 02:21:31 Re: Slow response of PostgreSQL
Previous Message Christopher Kings-Lynne 2004-02-18 01:50:00 Re: Slow response of PostgreSQL