Re: [COMMITTERS] pgsql-server: Rearrange pg_subtrans handling - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: [COMMITTERS] pgsql-server: Rearrange pg_subtrans handling
Date
Msg-id 200408252110.i7PLAUn15595@candle.pha.pa.us
Whole thread Raw
In response to Re: [COMMITTERS] pgsql-server: Rearrange pg_subtrans handling  (Christopher Kings-Lynne <chriskl@familyhealth.com.au>)
Responses Re: [COMMITTERS] pgsql-server: Rearrange pg_subtrans handling  (Alvaro Herrera <alvherre@dcc.uchile.cl>)
List 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@candle.pha.pa.us               |  (610)
359-1001+  If your life is a hard drive,     |  13 Roberts Road +  Christ can be your backup.        |  Newtown Square,
Pennsylvania19073
 


pgsql-hackers by date:

Previous
From: pgsql@mohawksoft.com
Date:
Subject: Contrib -- PostgreSQL shared variables
Next
From: Rick Gigger
Date:
Subject: Re: Contrib -- PostgreSQL shared variables