| From: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | M Simms <grim(at)argh(dot)demon(dot)co(dot)uk> |
| Cc: | pgsql-general(at)postgreSQL(dot)org |
| Subject: | Re: [GENERAL] Locking |
| Date: | 1999-05-03 01:59:30 |
| Message-ID: | 199905030159.VAA19221@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> What is the situation with locking in pustgresql
>
> I am aware that 6.5 has row level locking, and read-always, and that
> 6.4 doesnt (it just has complete table-level, if I am right).
>
> However that is moderately beside the point.
>
> What actually happens when I try and write to a table or row that is
> locked by another instance of the backend? Does it simply wait and try
> again, transparently, or do I have to handle this myself by checking on
> return statuses and retrying when I get a particular status? And is this
> also the case for reading a locked table in 6.4
It waits. All versions work this way.
--
Bruce Momjian | http://www.op.net/~candle
maillist(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Malkus | 1999-05-03 08:53:22 | (no subject) |
| Previous Message | M Simms | 1999-05-02 23:27:18 | Locking |