diff options
| author | Peter Eisentraut <peter@eisentraut.org> | 2020-02-06 21:21:04 +0100 |
|---|---|---|
| committer | Peter Eisentraut <peter@eisentraut.org> | 2020-02-06 21:25:01 +0100 |
| commit | fc7a5e9eaa2fa34b053ffe52e0e57f1fd6b1f939 (patch) | |
| tree | 4b066724f92bce87f4480d4215da978e94b83177 /src/backend/jit/llvm/llvmjit_expr.c | |
| parent | 7d4395d0a11589aa450a073d658c49b420f4493f (diff) | |
| download | postgresql-fc7a5e9eaa2fa34b053ffe52e0e57f1fd6b1f939.tar.gz postgresql-fc7a5e9eaa2fa34b053ffe52e0e57f1fd6b1f939.zip | |
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
Diffstat (limited to 'src/backend/jit/llvm/llvmjit_expr.c')
0 files changed, 0 insertions, 0 deletions