Re: [HACKERS] generated columns

Peter Eisentraut <peter.eisentraut@2ndquadrant.com>

From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>

To: Jeff Janes <jeff.janes@gmail.com>

Cc: Pavel Stehule <pavel.stehule@gmail.com>, Michael Paquier <michael@paquier.xyz>, pgsql-hackers <pgsql-hackers@postgresql.org>, Sergei Kornilov <sk@zsrv.org>, Jaime Casanova <jaime.casanova@2ndquadrant.com>

Date: 2019-04-01T08:53:27Z

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

Commits

Generated columns
- fc22b6623b6b 12.0 landed
Add walreceiver API to get remote server version
- 69039fda837d 12.0 landed
Add pg_partition_tree to display information about partitions
- d5eec4eefde7 12.0 cited
pg_restore: Augment documentation for -N option
- 2fe42baf7c1a 12.0 cited
Change delimiter used for display of NextXID
- 59a884e9854c 9.6.0 cited