| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | pgsql-committers(at)lists(dot)postgresql(dot)org |
| Subject: | pgsql: Preserve pg_index.indisreplident across REINDEX CONCURRENTLY |
| Date: | 2020-06-05 01:33:09 |
| Message-ID: | E1jh1EL-00046o-Nn@gemulon.postgresql.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
Preserve pg_index.indisreplident across REINDEX CONCURRENTLY
If the flag value is lost, logical decoding would work the same way as
REPLICA IDENTITY NOTHING, meaning that no old tuple values would be
included in the changes anymore produced by logical decoding.
Author: Michael Paquier
Reviewed-by: Euler Taveira
Discussion: https://postgr.es/m/20200603065340.GK89559@paquier.xyz
Backpatch-through: 12
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/1127f0e392c757fc4fbbeffd7d0202bb02670e9c
Modified Files
--------------
src/backend/catalog/index.c | 4 ++++
src/test/regress/expected/create_index.out | 21 +++++++++++++++++++++
src/test/regress/sql/create_index.sql | 11 +++++++++++
3 files changed, 36 insertions(+)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2020-06-05 09:19:03 | pgsql: OpenSSL 3.0.0 compatibility in tests |
| Previous Message | Tom Lane | 2020-06-04 21:57:36 | pgsql: Add missing #include. |