| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
| Cc: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Sergei Kornilov <sk(at)zsrv(dot)org>, Jaime Casanova <jaime(dot)casanova(at)2ndquadrant(dot)com> |
| Subject: | Re: [HACKERS] generated columns |
| Date: | 2019-04-01 08:53:27 |
| Message-ID: | fe2c53f8-db57-1d58-2d96-c992169a291c@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2019-03-31 15:22, Jeff Janes wrote:
> I can't do a same-major-version pg_upgrade across this commit, as the
> new pg_dump is trying to dump a nonexistent attgenerated column from the
> old database. Is that acceptable collateral damage? I thought we
> usually avoided that breakage within the dev branch, but I don't know
> how we do it.
We don't.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Page | 2019-04-01 09:09:05 | Re: GSoC proposal for pgAdmin 4 bytea support |
| Previous Message | Peter Eisentraut | 2019-04-01 08:52:27 | Re: [HACKERS] generated columns |