| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Jan Wieck <wieck(at)debis(dot)com> |
| Cc: | pgsql-hackers(at)postgreSQL(dot)org |
| Subject: | Re: [HACKERS] Weired FK problem |
| Date: | 1999-12-10 22:23:38 |
| Message-ID: | 199912102223.RAA01407@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> That's the behaviour I wanted to get from it. RI triggers
> need to see what's committed and what their own transaction
> did so far. That's HeapTupleSatisfiesNow().
>
> Since they lock everything they access, they simply force the
> old (pre MVCC) behaviour - wait if something is actually in
> use until the other transaction ends. No snapshots, no pain.
Sounds good.
--
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 | Jan Wieck | 1999-12-10 23:27:54 | Error in new psql |
| Previous Message | mdorman-pgsql.hackers | 1999-12-10 21:54:03 | Re: [HACKERS] postgresql authentification for popper |