Re: [HACKERS] Re: locking

From: Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us>
To: honza(at)ied(dot)com (Jan Vicherek)
Cc: pgsql-hackers(at)postgreSQL(dot)org, pgsql-questions(at)postgreSQL(dot)org
Subject: Re: [HACKERS] Re: locking
Date: 1998-01-21 15:05:17
Message-ID: 199801211505.KAA20684@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

>
>
> *Any* answers would be appreciated :
>
> I'll rephrase the original questions :
>
> pg doesn't have "row-level locking" but has "table locking".
> a result from a SELECT * FROM TESTTABLE; is a table.
> I lock the table (which is result of a SELECT).
>
> Q : will this locking prevent update of the rows in TESTTABLE that have
> been SELECTed ?
>

While the SELECT is running, no one can update the table. If the SELECT
is in a transaction, no one can update the table until the transaction
completes. Other people can read from the table, though.

--
Bruce Momjian
maillist(at)candle(dot)pha(dot)pa(dot)us

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 1998-01-21 15:09:37 Re: [HACKERS] Re: subselects
Previous Message Serj 1998-01-21 14:56:50 group by bug in 6.2.1 & 6.3 -snapshot