Re: BUG #4817: Dump of 8.3 hstore not restorable to 8.4 (RECHECK)
От | David Blewett |
---|---|
Тема | Re: BUG #4817: Dump of 8.3 hstore not restorable to 8.4 (RECHECK) |
Дата | |
Msg-id | 9d1f8d830905200617s43ddb8f5t92537464a64e1042@mail.gmail.com обсуждение исходный текст |
Ответ на | BUG #4817: Dump of 8.3 hstore not restorable to 8.4 (RECHECK) ("David Blewett" <david@dawninglight.net>) |
Ответы |
Re: BUG #4817: Dump of 8.3 hstore not restorable to 8.4 (RECHECK)
|
Список | 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 по дате отправления: