| From: | momjian(at)svr1(dot)postgresql(dot)org (Bruce Momjian) |
|---|---|
| To: | pgsql-committers(at)postgresql(dot)org |
| Subject: | pgsql-server: Update item: < * Implement dirty reads or shared row |
| Date: | 2004-08-24 11:09:45 |
| Message-ID: | 20040824110945.31FBB5E4844@svr1.postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
Log Message:
-----------
Update item:
< * Implement dirty reads or shared row locks and use them in RI triggers (?)
> * Implement dirty reads or shared row locks and use them in RI triggers
>
> Adding shared locks requires recording the table/rows numbers in a
> shared area, and this could potentially be a large amount of data.
> One idea is to store the table/row numbers in a separate table and set
> a bit on the row indicating looking in this new table is required to
> find any shared row locks.
>
Modified Files:
--------------
pgsql-server/doc:
TODO (r1.1342 -> r1.1343)
(http://developer.postgresql.org/cvsweb.cgi/pgsql-server/doc/TODO.diff?r1=1.1342&r2=1.1343)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Marc G. Fournier | 2004-08-24 11:50:44 | Re: pgsql-server: Update that 8.0 will support MS Win |
| Previous Message | Bruce Momjian | 2004-08-24 11:06:36 | Re: [COMMITTERS] pgsql-server: Rearrange pg_subtrans handling |