Re: [HACKERS] Another nasty cache problem

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: Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: [HACKERS] Another nasty cache problem
Date: 2000-02-01 01:54:27
Message-ID: 200002010154.UAA21581@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> I am starting to think that Bruce's idea might be the way to go: lock
> down any cache entry that's been referenced since the last transaction
> start or CommandCounterIncrement, and elog() if it's changed by
> invalidation. Then the only coding rule needed is "cached tuples don't
> stay valid across CommandCounterIncrement", which is relatively
> simple to check for.

Yea, I had a good idea ...

--
Bruce Momjian | http://www.op.net/~candle
pgman(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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2000-02-01 01:54:45 Re: [HACKERS] Re: Case-folding bogosity in new psql
Previous Message Bruce Momjian 2000-02-01 01:51:55 Re: [HACKERS] Re: [ADMIN] Attribute 'aggtransfn1' is repeated