Ensure relcache consistency around generated columns
authorPeter Eisentraut <peter@eisentraut.org>
Thu, 6 Feb 2020 20:21:04 +0000 (21:21 +0100)
committerPeter Eisentraut <peter@eisentraut.org>
Thu, 6 Feb 2020 20:25:01 +0000 (21:25 +0100)
commitfc7a5e9eaa2fa34b053ffe52e0e57f1fd6b1f939
tree4b066724f92bce87f4480d4215da978e94b83177
parent7d4395d0a11589aa450a073d658c49b420f4493f
Ensure relcache consistency around generated columns

In certain transient states, it's possible that a table has attributes
with attgenerated set but no default expressions in pg_attrdef yet.
In that case, the old code path would not set
relation->rd_att->constr->has_generated_stored, unless
relation->rd_att->constr was also populated for some other reason.
There was probably no practical impact, but it's better to keep this
consistent.

Reported-by: Andres Freund <andres@anarazel.de>
Discussion: https://www.postgresql.org/message-id/flat/20200115181105.ad6ab6dlgyww3lb6%40alap3.anarazel.de
src/backend/utils/cache/relcache.c