diff options
| author | Alexander Korotkov <akorotkov@postgresql.org> | 2023-10-28 00:21:23 +0300 |
|---|---|---|
| committer | Alexander Korotkov <akorotkov@postgresql.org> | 2023-10-28 00:21:23 +0300 |
| commit | 5ae2087202af9fd804c8b8d76954bdd8bdf31e51 (patch) | |
| tree | a8526a8051cec6ce8bb55a7d449828ae57b47734 /src/backend/executor/nodeFunctionscan.c | |
| parent | 8b62b441fffd26f0bfaa5bed2c11898ed1345f62 (diff) | |
| download | postgresql-5ae2087202af9fd804c8b8d76954bdd8bdf31e51.tar.gz postgresql-5ae2087202af9fd804c8b8d76954bdd8bdf31e51.zip | |
Teach contrib/amcheck to check the unique constraint violation
Add the 'checkunique' argument to bt_index_check() and bt_index_parent_check().
When the flag is specified the procedures will check the unique constraint
violation for unique indexes. Only one heap entry for all equal keys in
the index should be visible (including posting list entries). Report an error
otherwise.
pg_amcheck called with the --checkunique option will do the same check for all
the indexes it checks.
Author: Anastasia Lubennikova <lubennikovaav@gmail.com>
Author: Pavel Borisov <pashkin.elfe@gmail.com>
Author: Maxim Orlov <orlovmg@gmail.com>
Reviewed-by: Mark Dilger <mark.dilger@enterprisedb.com>
Reviewed-by: Zhihong Yu <zyu@yugabyte.com>
Reviewed-by: Peter Geoghegan <pg@bowt.ie>
Reviewed-by: Aleksander Alekseev <aleksander@timescale.com>
Discussion: https://postgr.es/m/CALT9ZEHRn5xAM5boga0qnrCmPV52bScEK2QnQ1HmUZDD301JEg%40mail.gmail.com
Diffstat (limited to 'src/backend/executor/nodeFunctionscan.c')
0 files changed, 0 insertions, 0 deletions