Re: Well, we seem to be proof against cache-inval problems now

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: Well, we seem to be proof against cache-inval problems now
Date: 2001-01-10 02:32:00
Message-ID: 200101100232.VAA21606@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

No? :-)

> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> >> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> >>>> Can this now be marked as done?
> >>>> * Modification of pg_class can happen while table in use by another
> >>>> backend. Might lead to MVCC inside of syscache
> >>
> >> I'm not sure. Do you have any record of what the concern was, in
> >> detail? I don't understand what the TODO item is trying to say.
>
> > I assumed it was the problem of table lookups with no locking. No idea
> > what the MVCC mention is about.
>
> I checked the CVS archives and found that you added that TODO item on
> 4-Feb-2000. I could not, however, find any relevant discussion in the
> pghackers archives in the first few days of February. Do you have
> anything archived that might help narrow it down?
>
> regards, tom lane
>

--
Bruce Momjian | http://candle.pha.pa.us
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 2001-01-10 02:32:18 Re: Well, we seem to be proof against cache-inval problems now
Previous Message Tatsuo Ishii 2001-01-10 01:58:59 Re: Re: [HACKERS] How to print explain using PHP