Re: Can we remove SnapshotSelf?

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Can we remove SnapshotSelf?
Date: 2005-02-25 04:59:36
Message-ID: 200502250459.j1P4xae07699@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
> As of CVS tip, there is no code in the system that uses SnapshotSelf.
> I am wondering if we can get rid of it and thereby save one test in
> the heavily used HeapTupleSatisfiesVisibility() macro.
>
> There is one place in the foreign-key triggers that uses the underlying
> HeapTupleSatisfiesItself() test directly. So it seems possible that we
> might someday need SnapshotSelf again as the representation of the
> appropriate snapshot test for a foreign-key check. But I suspect that
> any future changes in the FK stuff will go in the direction of using
> dirty reads instead. In any case we could always put back SnapshotSelf
> if we needed it.
>
> Comments?

I think we should either remove it or mark it as NOT_USED.

--
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

Browse pgsql-hackers by date

  From Date Subject
Next Message Greg Stark 2005-02-25 05:07:01 Re: [pgsql-hackers-win32] win32 performance - fsync question
Previous Message Bruce Momjian 2005-02-25 04:51:16 Re: UTF8 or Unicode