diff options
| author | Amit Kapila <akapila@postgresql.org> | 2023-07-14 08:21:54 +0530 |
|---|---|---|
| committer | Amit Kapila <akapila@postgresql.org> | 2023-07-14 08:21:54 +0530 |
| commit | edca3424342da323499a1998d18a888283e52ac7 (patch) | |
| tree | 42923ac76129cacb6deaf33581c67cb6c2e87a1a /doc/src | |
| parent | a5ea825f958c2de9fadb825cbf16bf9b1360f0df (diff) | |
| download | postgresql-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 'doc/src')
| -rw-r--r-- | doc/src/sgml/logical-replication.sgml | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/src/sgml/logical-replication.sgml b/doc/src/sgml/logical-replication.sgml index c2a749d8828..e71f4bac69c 100644 --- a/doc/src/sgml/logical-replication.sgml +++ b/doc/src/sgml/logical-replication.sgml @@ -134,9 +134,9 @@ to replica identity <literal>FULL</literal>, which means the entire row becomes the key. When replica identity <literal>FULL</literal> is specified, indexes can be used on the subscriber side for searching the rows. Candidate - indexes must be btree, non-partial, and the leftmost index field must be a - column (not an expression) that references the published table column. These - restrictions on the non-unique index properties adhere to some of the + indexes must be btree or hash, non-partial, and the leftmost index field must + be a column (not an expression) that references the published table column. + These restrictions on the non-unique index properties adhere to some of the restrictions that are enforced for primary keys. If there are no such suitable indexes, the search on the subscriber side can be very inefficient, therefore replica identity <literal>FULL</literal> should only be used as a |