| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: DropRelFileNodeBuffers API change (was Re: [BUGS] BUG #5599: Vacuum fails due to index corruption issues) |
| Date: | 2010-08-15 21:39:08 |
| Message-ID: | 5884.1281908348@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> I really hate this solution, because writing out data that we're about
> to throw away just in case we can't actually throw it away seems like
> a real waste from a performance standpoint.
We went around on this already in the pgsql-bugs thread. I don't much
like it either, but there isn't any better solution that seems safe
enough to back-patch.
> Could we avoid this
> altogether by allocating a new relfilenode on truncate?
Then we'd have to copy all the data we *didn't* truncate, which is
hardly likely to be a win.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2010-08-15 21:42:43 | Re: DropRelFileNodeBuffers API change (was Re: [BUGS] BUG #5599: Vacuum fails due to index corruption issues) |
| Previous Message | Greg Stark | 2010-08-15 21:17:54 | Re: DropRelFileNodeBuffers API change (was Re: [BUGS] BUG #5599: Vacuum fails due to index corruption issues) |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2010-08-15 21:42:43 | Re: DropRelFileNodeBuffers API change (was Re: [BUGS] BUG #5599: Vacuum fails due to index corruption issues) |
| Previous Message | Tom Lane | 2010-08-15 21:29:48 | Re: Inconsistent ::bit(N) and get_bit()? |