Re: Prepping to break every past release... - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: Prepping to break every past release...
Date
Msg-id 1236674788.31880.352.camel@ebony.2ndQuadrant
Whole thread Raw
In response to Re: Prepping to break every past release...  (Andrew Gierth <andrew@tao11.riddles.org.uk>)
Responses Re: Prepping to break every past release...  (Andrew Gierth <andrew@tao11.riddles.org.uk>)
Re: Prepping to break every past release...  (David Fetter <david@fetter.org>)
List pgsql-hackers
On Thu, 2009-03-05 at 01:27 +0000, Andrew Gierth wrote:

> Now, of course, counting the upcoming 8.4 there have been three (and a
> bit - the original design predates 8.1, though it did anticipate some
> 8.1 features) new releases against which the original concept can be
> tested. And, guess what, nothing in those releases has even come close
> to invalidating the original design concept (as we knew all along).
> 
> If you're still not convinced of that fact, it would be possible to
> take the original design and update it to 8.4 following the original
> plan. But I'm not prepared to spend any time on this if the only
> result is going to be more argument.

I see the use for some more stable views.

Would it be better to publish them as an external project? That way we
can still use them for both old and new releases. Once the project takes
hold it might then be included in core - but that's not hugely important
if you can persuade people to include the project with the Windows
installer.

The problem with anything included in core is that we don't/can't
quickly fix design flaws, so even if we did get something in now it
might not do everything we want (and then we'd have to change it...).

-- Simon Riggs           www.2ndQuadrant.comPostgreSQL Training, Services and Support



pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: One less footgun: deprecating pg_dump -d
Next
From: Hannu Krosing
Date:
Subject: Re: Updates of SE-PostgreSQL 8.4devel patches (r1704)