From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | David Blewett <david(at)dawninglight(dot)net> |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #4817: Dump of 8.3 hstore not restorable to 8.4 (RECHECK) |
Date: | 2009-05-26 22:08:30 |
Message-ID: | 20073.1243375710@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
I wrote:
> If we remove the RECHECK printout then this will stop being true ---
> and worse, it will break silently and in a way that will only cause
> you to get occasional wrong answers from your queries.
But actually, that only says it's a bad idea to drop RECHECK from the
pg_dump output. It doesn't say that an 8.4 server has to throw error
when it sees RECHECK. The way things are set up now, ignoring it seems
fairly failsafe. The default assumption in 8.4 is that operators are
lossy, so the worst case consequence is that you waste cycles on
unnecessary rechecks. You don't get wrong answers, even if you
neglected to update your opclass support code.
Off to make a proposal to pghackers ...
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Herbert Bonaffini | 2009-05-27 15:43:29 | BUG #4825: Before installation the server not running |
Previous Message | Tom Lane | 2009-05-26 20:13:03 | Re: BUG #4817: Dump of 8.3 hstore not restorable to 8.4 (RECHECK) |