| From: | Leslie Mikesell <les(at)Mcs(dot)Net> |
|---|---|
| To: | maillist(at)candle(dot)pha(dot)pa(dot)us (Bruce Momjian) |
| Cc: | honza(at)ied(dot)com, pgsql-hackers(at)postgreSQL(dot)org, pgsql-questions(at)postgreSQL(dot)org |
| Subject: | Re: [QUESTIONS] Re: [HACKERS] Re: locking |
| Date: | 1998-01-21 15:55:03 |
| Message-ID: | 199801211555.JAA05611@Mars.mcs.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> >
> > 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.
Does only one transaction run at a time? That is, if you have a
transaction from client A that does a select followed by an update
and client B attempts the same thing, will the read portion of
B's transaction be deferred until A's commit completes, while
a non-transaction select (read only) from B would be allowed to
proceed?
Les Mikesell
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 1998-01-21 15:56:37 | Re: [HACKERS] subselects |
| Previous Message | The Hermit Hacker | 1998-01-21 15:39:54 | Re: [PORTS] -current version won't initdb under i386_solaris... |