| From: | "Mikheev, Vadim" <vmikheev(at)SECTORBASE(dot)COM> |
|---|---|
| To: | "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Jan Wieck <JanWieck(at)Yahoo(dot)com>, Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | RE: TOAST-table vacuuming (was Re: Idea for reducing pl anning time) |
| Date: | 2000-12-15 20:13:59 |
| Message-ID: | 8F4C99C66D04D4118F580090272A7A234D31FC@sectorbase1.sectorbase.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> > Also, is TOAST-table vacuuming fixed now?
>
> Still broken. Hiroshi had muttered something about fixing
> the internal commit of VACUUM so that it's more like a real
> commit --- including advancing the transaction ID --- but
> still doesn't release the exclusive lock held by VACUUM.
> Basically we need to propagate the locks forward to the new
> xact instead of releasing them. I think that would be a nice
> clean solution if we could do it. Do you have any ideas about how?
Yes, it would be nice for cursors too - they should be able to cross
transaction boundaries...
Use BackendID instead of XID in XIDTAG?
Add internal (ie per backend) hash of locks that should not be
released at commit time?
And couple additional funcs in lmgr API?
Vadim
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2000-12-15 20:20:27 | Re: Idea for reducing planning time |
| Previous Message | Bruce Momjian | 2000-12-15 20:07:46 | Re: Idea for reducing planning time |