From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
---|---|
To: | "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: First draft of back-branch release notes is done |
Date: | 2019-08-08 17:15:53 |
Message-ID: | 20190808171553.GA21274@alvherre.pgsql |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
I realize that this has now been sent, but I wanted to comment on one
item:
On 2019-Aug-04, Jonathan S. Katz wrote:
> * Ensure that partition key columns will not be dropped as the result of an
> "indirect drop," such as from a cascade from dropping the key column's data
> type (e.g. a custom data type). This fix is applied only to newly created
> partitioned tables: if you believe you have an affected partition table (e.g.
> one where the partition key uses a custom data type), you will need to
> create a new table and move your data into it.
Hmm, if I have this problem, I can pg_upgrade and the new database will
have correct dependencies, right? For some people, doing that might be
easier than creating and reloading large tables.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Ibrar Ahmed | 2019-08-08 17:25:15 | Re: Small const correctness patch |
Previous Message | Alvaro Herrera | 2019-08-08 17:07:25 | Re: Small patch to fix build on Windows |