pgsql: Ensure relcache consistency around generated columns

From: Peter Eisentraut <peter(at)eisentraut(dot)org>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Ensure relcache consistency around generated columns
Date: 2020-02-06 20:29:11
Message-ID: E1iznlv-0005I7-5x@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

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(at)anarazel(dot)de>
Discussion: https://www.postgresql.org/message-id/flat/20200115181105.ad6ab6dlgyww3lb6%40alap3.anarazel.de

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/fc7a5e9eaa2fa34b053ffe52e0e57f1fd6b1f939

Modified Files
--------------
src/backend/utils/cache/relcache.c | 7 +++++--
1 file changed, 5 insertions(+), 2 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Michael Paquier 2020-02-06 23:11:59 pgsql: Revert "Add GUC checks for ssl_min_protocol_version and ssl_max_
Previous Message Jeff Davis 2020-02-06 20:09:07 pgsql: Refactor hash_agg_entry_size().