| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
| Cc: | Teodor Sigaev <teodor(at)sigaev(dot)ru>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [BUGS] BUG #14155: bloom index error with unlogged table |
| Date: | 2016-06-04 03:55:34 |
| Message-ID: | 22343.1465012534@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
Jeff Janes <jeff(dot)janes(at)gmail(dot)com> writes:
> One thing from the commit-message:
> "On-disk, we can still store it in words, so as to not break on-disk
> compatibility with beta1."
> Hasn't that ship already sailed?
No.
> Or is the concern about intra-version pg_upgrade rather than direct
> on-disk compatibility?
This. You can pg_upgrade across a catversion bump, but not across
changes in user table or index contents.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2016-06-05 15:54:56 | Re: BUG #14134: segmentation fault with large table with gist index |
| Previous Message | Jeff Janes | 2016-06-04 03:27:05 | Re: [BUGS] BUG #14155: bloom index error with unlogged table |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Masahiko Sawada | 2016-06-04 04:18:38 | Re: Reviewing freeze map code |
| Previous Message | Tom Lane | 2016-06-04 03:50:03 | Re: IPv6 link-local addresses and init data type |