Re: BUG #4817: Dump of 8.3 hstore not restorable to 8.4 (RECHECK) - Mailing list pgsql-bugs

From David Blewett
Subject Re: BUG #4817: Dump of 8.3 hstore not restorable to 8.4 (RECHECK)
Date
Msg-id 9d1f8d830905200617s43ddb8f5t92537464a64e1042@mail.gmail.com
Whole thread Raw
In response to BUG #4817: Dump of 8.3 hstore not restorable to 8.4 (RECHECK)  ("David Blewett" <david@dawninglight.net>)
Responses Re: BUG #4817: Dump of 8.3 hstore not restorable to 8.4 (RECHECK)
List pgsql-bugs
On Wed, May 20, 2009 at 8:48 AM, David Blewett <david@dawninglight.net>wrote:

>
> In testing the beta to see if my planner issues might be resolved, I ran
> into a situation where the 8.4 pg_dump created a dump for the hstore
> contrib
> module which would not restore against 8.4.


It looks like this relates back to the "Remove lossy-operator RECHECK flag?"
discussion [1] last April. That seemed to end with this decision:

> For the moment I have it doing #1, but it strikes me that that is only
> useful if 8.4 getsto release without having made any backwards-incompatible
> changes in pg_dump output, which is probably not better than a fifty-fifty
> bet.
>

Has there been any backwards-incompatible changes since then?

David Blewett

1. http://archives.postgresql.org/message-id/19212.1208122532@sss.pgh.pa.us

pgsql-bugs by date:

Previous
From: "David Blewett"
Date:
Subject: BUG #4817: Dump of 8.3 hstore not restorable to 8.4 (RECHECK)
Next
From: "Alexei"
Date:
Subject: BUG #4819: Ordering big tables by indexed columns is very slow.