| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | Alvaro Herrera <alvherre(at)atentus(dot)com>, pgsql-patches(at)postgresql(dot)org |
| Subject: | Re: CLUSTER patch |
| Date: | 2002-07-14 18:25:52 |
| Message-ID: | 19971.1026671152@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches |
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> Yep, I think everything now points to changes needed in relcache.c to
> handle the new condition of a relation swapping its relnode.
I still don't believe that any changes are needed in relcache.c.
In particular, after thinking more I see that we do not need to change
the myxactonly status of either relation: the temp one is still temp,
the original one is still not.
What we do need to do is to flush all buffers for the two rels from the
local and global buffer caches respectively, since after the swap they
should get buffered in different places. FlushRelationBuffers looks
like it will work for that.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2002-07-14 18:46:50 | Re: CLUSTER patch |
| Previous Message | Bruce Momjian | 2002-07-14 17:54:10 | Re: CLUSTER patch |