Re: 9.1 release scheduling (was Re: reducing the overhead of frequent table locks - now, with WIP patch)
Alvaro Herrera <alvherre@commandprompt.com>
From: Alvaro Herrera <alvherre@commandprompt.com>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Thom Brown <thom@linux.com>, Tom Lane <tgl@sss.pgh.pa.us>, Joshua Berkus <josh@agliodbs.com>, Dave Page <dpage@pgadmin.org>, Stephen Frost <sfrost@snowman.net>, Dimitri Fontaine <dimitri@2ndquadrant.fr>, Simon Riggs <simon@2ndquadrant.com>, Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2011-06-08T01:25:30Z
Lists: pgsql-hackers
Excerpts from Robert Haas's message of mar jun 07 13:53:23 -0400 2011: > On Tue, Jun 7, 2011 at 1:45 PM, Thom Brown <thom@linux.com> wrote: > > Speaking of which, is it now safe to remove the "NOT VALID constraints > > don't dump properly" issue from the blocker list since the fix has > > been committed? > > I hope so, because I just did that (before noticing this email from you). Yeah, pg_dump works in HEAD ... the bug now is that psql prints "NOT VALID" twice. Will fix. -- Álvaro Herrera <alvherre@commandprompt.com> The PostgreSQL Company - Command Prompt, Inc. PostgreSQL Replication, Consulting, Custom Development, 24x7 support