Re: Schedule for 8.1 feature freeze

From: "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>
To: "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>, "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Schedule for 8.1 feature freeze
Date: 2005-06-21 07:49:26
Message-ID: E7F85A1B5FF8D44C8A1AF6885BC9A0E490E5C7@ratbert.vale-housing.co.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> -----Original Message-----
> From: pgsql-hackers-owner(at)postgresql(dot)org
> [mailto:pgsql-hackers-owner(at)postgresql(dot)org] On Behalf Of Bruce Momjian
> Sent: 21 June 2005 05:04
> To: PostgreSQL-development
> Subject: [HACKERS] Schedule for 8.1 feature freeze
>
> We have addressed all the open issues for 8.1 except for auto-vacuum,
> which Alvaro is working on, so I think we are ready for a
> feature freeze
> on July 1.

What about Andreas' instrumentation stuff? This has been going on since
before 8.0 and it would good to get it in 8.1 given the amount of extra
functionality it allows us to offer users that prefer a GUI interface.

I realise there probably won't be time to fix pg_terminate_backend, or
convince people that it offers the admin the lesser of two evils (my
limited understanding being that there is a chance of it not clearing
some locks, vs, having to shut down the whole server to kill a single
connection) - can we at least get the other functions applied?

Thanks, Dave.

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Magnus Hagander 2005-06-21 07:50:29 Re: Schedule for 8.1 feature freeze
Previous Message Dave Page 2005-06-21 07:41:13 Re: [PATCHES] default database creation with initdb