| From: | David Blewett <david(at)dawninglight(dot)net> |
|---|---|
| To: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #4817: Dump of 8.3 hstore not restorable to 8.4 (RECHECK) |
| Date: | 2009-05-20 13:17:10 |
| Message-ID: | 9d1f8d830905200617s43ddb8f5t92537464a64e1042@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Wed, May 20, 2009 at 8:48 AM, David Blewett <david(at)dawninglight(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alexei | 2009-05-21 01:04:28 | BUG #4819: Ordering big tables by indexed columns is very slow. |
| Previous Message | David Blewett | 2009-05-20 12:48:34 | BUG #4817: Dump of 8.3 hstore not restorable to 8.4 (RECHECK) |