Ensure relcache consistency around generated columns
Peter Eisentraut <peter@eisentraut.org>
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
Files
| Path | Change | +/− |
|---|---|---|
| src/backend/utils/cache/relcache.c | modified | +5 −2 |
Discussion
- relcache sometimes initially ignores has_generated_stored 4 messages · 2020-01-15 → 2020-02-06