| 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: | Scott Marlowe <scott(dot)marlowe(at)ihs(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Subject: bool / vacuum full bug followup part 2 |
| Date: | 2002-06-03 23:43:41 |
| Message-ID: | 13052.1023147821@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> Tom Lane wrote:
>> Yes, and yes, but don't hold your breath on the latter part --- that
>> TODO item has been around for awhile. And it's gotten harder now that
>> we have lazy VACUUM; that means we need to be able to condense indexes
>> concurrently with other index operations.
> Can you remind me why it is so hard to fix this. I do not expect lazy
> vacuum to handle index shrinking, but it should be possible with full
> vacuum.
If you make that restriction then it might be less painful to do. I
have not thought about doing it that way; I'm of the opinion that only
a solution that lets lazy vacuum do it will be a real solution.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2002-06-03 23:48:19 | Re: strangeness in pg_dump |
| Previous Message | Tom Lane | 2002-06-03 23:41:09 | Re: Vacuum behaviour in plpgsql function |