| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | Rushabh Lathia <rushabh(dot)lathia(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg_dump: fail to restore partition table with serial type |
| Date: | 2019-06-13 00:46:57 |
| Message-ID: | 30015.1560386817@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> writes:
> There was indeed one more problem, that only the pg10 pg_upgrade test
> detected. Namely, binary-upgrade dump didn't restore for locally
> defined constraints: they were dumped twice, first in the table
> definition and later by the ALTER TABLE ADD CONSTRAINT bit for binary
> upgrade that I had failed to notice. Ooops. The reason pg10 detected
> it and the other branches didn't, is that the only constraint of this
> ilk that remained after running regress was removed by 05bd889904e0 :-(
Seems like we'd better put back some coverage for that case, no?
But I'm confused by your reference to 05bd889904e0. It looks like
that didn't change anything about tables that weren't getting dropped
anyhow.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2019-06-13 01:34:27 | Re: PG 12 draft release notes |
| Previous Message | Tom Lane | 2019-06-13 00:37:21 | Re: proposal: new polymorphic types - commontype and commontypearray |