Re: Fast default stuff versus pg_upgrade
Andres Freund <andres@anarazel.de>
From: Andres Freund <andres@anarazel.de>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Andrew Dunstan <andrew@dunslane.net>, pgsql-hackers@lists.postgresql.org
Date: 2018-06-19T16:52:20Z
Lists: pgsql-hackers
Hi, On 2018-06-19 12:37:52 -0400, Tom Lane wrote: > Andres Freund <andres@anarazel.de> writes: > > And if the default value bugs us, > > we can easily add a support function that dumps the value without the > > anyarray adornment? > > The problem here is that that function does not exist in 11beta1. > Since adding the "incoming" function is certainly going to require > initdb, we have to be able to dump from the server as it now stands, > or we'll be cutting existing beta testers adrift. It'd probably not be too hard to write a plpgsql replacement for it, should it come to that. Obviously it'd be nicer to not require users to create that, but ... Greetings, Andres Freund
Commits
-
Allow for pg_upgrade of attributes with missing values
- 2448adf29c54 11.0 landed