Re: How about closing some Open Items? - Mailing list pgsql-hackers

From Robert Haas
Subject Re: How about closing some Open Items?
Date
Msg-id AANLkTilPn91ydRBrb6oxuN3Yw1ZDYiJCRS23JI3QAKaV@mail.gmail.com
Whole thread Raw
In response to How about closing some Open Items?  (Josh Berkus <josh@agliodbs.com>)
Responses Re: How about closing some Open Items?  (Josh Berkus <josh@agliodbs.com>)
Re: How about closing some Open Items?  (Alvaro Herrera <alvherre@commandprompt.com>)
List pgsql-hackers
On Tue, Jun 8, 2010 at 1:32 PM, Josh Berkus <josh@agliodbs.com> wrote:
> However, I haven't see much progress in the last 10 days on closing any
> of these issues, and quite a few people have moved on to 9.1 features.

I appreciate the effort that went into making this list, but it's not
very useful to work off of any more.  The problem is that the set of
things that is listed here is pretty erratic - there are actual
problems that are not on this list, and there are things on this list
that are 100% unimportant.  In particular, pretty much everything in
the docs section is crap.  Just because two people discussed something
at some point in the last six months doesn't make it an open issue.
Most of those conversations were not pursued because they were not
deemed important enough to pursuing, and I think only one of them has
an actual patch associated with it, viz:

ALTER TABLE .. DISABLE/ENABLE TRIGGER are out of date

I took a look at that patch, and I expect it's probably correct, but I
haven't actually looked at the code to verify that it's correct, so I
didn't apply it.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Idea for getting rid of VACUUM FREEZE on cold pages
Next
From: Simon Riggs
Date:
Subject: Re: primary/secondary/master/slave/standby