Re: [COMMITTERS] pgsql-server: Rearrange pg_subtrans handling

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com>, Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [COMMITTERS] pgsql-server: Rearrange pg_subtrans handling
Date: 2004-08-25 21:10:30
Message-ID: 200408252110.i7PLAUn15595@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

Christopher Kings-Lynne wrote:
> > OK, TODO updated:
> >
> > * Implement dirty reads or shared row locks and use them in RI triggers
>
> Can someone explain to me what a dirty read is and how it relates to RI
> triggers?

Dirty read allows you to see uncommited rows. I think RI triggers need
it so they can know if someone has a current transaction that is going
to conflict with the RI trigger action, or something like that. Right
now I think we hang waiting for the transaction to complete.

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Alvaro Herrera 2004-08-25 21:44:22 Re: [COMMITTERS] pgsql-server: Rearrange pg_subtrans handling
Previous Message Tom Lane 2004-08-25 20:07:57 pgsql-server: Fix typo in comment, per Andrew Dunstan.

Browse pgsql-hackers by date

  From Date Subject
Next Message pgsql 2004-08-25 21:15:28 Contrib -- PostgreSQL shared variables
Previous Message Hicham G. Elmongui 2004-08-25 20:24:06 printing HeapTuple