aboutsummaryrefslogtreecommitdiff
path: root/src/backend/utils/adt/arrayfuncs.c
diff options
context:
space:
mode:
authorAmit Kapila <akapila@postgresql.org>2023-07-14 08:21:54 +0530
committerAmit Kapila <akapila@postgresql.org>2023-07-14 08:21:54 +0530
commitedca3424342da323499a1998d18a888283e52ac7 (patch)
tree42923ac76129cacb6deaf33581c67cb6c2e87a1a /src/backend/utils/adt/arrayfuncs.c
parenta5ea825f958c2de9fadb825cbf16bf9b1360f0df (diff)
downloadpostgresql-edca3424342da323499a1998d18a888283e52ac7.tar.gz
postgresql-edca3424342da323499a1998d18a888283e52ac7.zip
Allow the use of a hash index on the subscriber during replication.
Commit 89e46da5e5 allowed using BTREE indexes that are neither PRIMARY KEY nor REPLICA IDENTITY on the subscriber during apply of update/delete. This patch extends that functionality to also allow HASH indexes. We explored supporting other index access methods as well but they don't have a fixed strategy for equality operation which is required by the current infrastructure in logical replication to scan the indexes. Author: Kuroda Hayato Reviewed-by: Peter Smith, Onder Kalaci, Amit Kapila Discussion: https://postgr.es/m/TYAPR01MB58669D7414E59664E17A5827F522A@TYAPR01MB5866.jpnprd01.prod.outlook.com
Diffstat (limited to 'src/backend/utils/adt/arrayfuncs.c')
0 files changed, 0 insertions, 0 deletions