Missing CONCURRENT VACUUM (Was: Release notes for 8.1)

From: Hannu Krosing <hannu(at)skype(dot)net>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Missing CONCURRENT VACUUM (Was: Release notes for 8.1)
Date: 2005-08-16 21:01:57
Message-ID: 1124226118.31798.55.camel@fuji.krosing.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Once more:

I would like to get at least some answer, why my patch for enabling
concurrent VACUUM was left out from 8.1.

It was submitted well in time, and there was only minimal amount of
discussion of an earlier patch,and AFAIK I addressed all the issues
raised there.

I really hate to have to start maintaining my own patches for "24/7,
OLTP-enabled" postgreSQL, at least unless I know that there is a good
reason why the mainline postgreSQL can't have these.

--
Hannu Krosing <hannu(at)skype(dot)net>

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Gregory Maxwell 2005-08-16 21:09:24 Re: pl/Ruby, deprecating plPython and Core
Previous Message Hannu Krosing 2005-08-16 20:47:21 Re: pl/Ruby, deprecating plPython and Core