Re: TOAST-table vacuuming (was Re: Idea for reducing planning time)

From: Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp>
To: "Mikheev, Vadim" <vmikheev(at)SECTORBASE(dot)COM>
Cc: "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Jan Wieck <JanWieck(at)Yahoo(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: TOAST-table vacuuming (was Re: Idea for reducing planning time)
Date: 2000-12-18 00:41:39
Message-ID: 3A3D5D43.5A9E1B49@tpf.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"Mikheev, Vadim" wrote:
>
> > > 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...
>

Cursors outside transactions is a nice feature I've
long wanted.
It would be nice if one of the requirement is solved.

How many factors should be solved to achieve it ?
For example,not release the buffers kept by such
cursors ...

Regards.
Hiroshi Inoue

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2000-12-18 01:05:40 Re: Tuple data
Previous Message Hiroshi Inoue 2000-12-18 00:10:21 Re: Tuple data