From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Vadim Mikheev <vadim(at)krs(dot)ru> |
Cc: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us>, pgsql-hackers(at)postgreSQL(dot)org |
Subject: | Re: [HACKERS] Ye olde "relation doesn't quite exist" problem |
Date: | 1999-06-04 03:34:35 |
Message-ID: | 13539.928467275@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Vadim Mikheev <vadim(at)krs(dot)ru> writes:
> Bruce Momjian wrote:
>> Thanks. I am a little confused. I thought you just flushed only on
> ^^^^^^^^^^^^^^^^^^^^
>> elog()/abort. How does the new code work.
> ^^^^^^^^^^^^
> It seems as more right thing to do.
What I just committed does the cache flush whenever
RelationFlushRelation is called --- in particular, elog/abort will
cause it to happen if there are any created-in-current-transaction
relations to be disposed of. But otherwise, no flush.
The obvious question about that is "what about modifications to
cacheable tuples that are not triggered by a relation creation?"
I think that those cases are OK because they are covered by the
shared-invalidation code. At least, we have no bug reports to
prove the contrary...
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 1999-06-04 03:43:40 | Re: [HACKERS] Re: Freezing docs for v6.5 |
Previous Message | Vadim Mikheev | 1999-06-04 03:31:34 | Re: [HACKERS] Open 6.5 items |