Postgres Pro
Downloads
Home   >   mailing lists

doc: improve the restriction description of using indexes on REPLICA IDENTITY FULL table. - Mailing list pgsql-hackers

From Masahiko Sawada
Subject doc: improve the restriction description of using indexes on REPLICA IDENTITY FULL table.
Date
Msg-id CAD21AoDJjffEvUFKXT27Q5U8-UU9JHv4rrJ9Ke8Zkc5UPWHLvA@mail.gmail.com
Whole thread Raw
Responses Re: doc: improve the restriction description of using indexes on REPLICA IDENTITY FULL table.
Re: doc: improve the restriction description of using indexes on REPLICA IDENTITY FULL table.
List pgsql-hackers
Tree view 
Hi,

Commit 89e46da5e5 allowed us to use indexes for searching on REPLICA
IDENTITY FULL tables. The documentation explains:

When replica identity <quote>full</quote> is specified,
indexes can be used on the subscriber side for searching the rows.  Candidate
indexes must be btree, non-partial, and have at least one column reference
(i.e. cannot consist of only expressions).

To be exact, IIUC the column reference must be on the leftmost column
of indexes. Does it make sense to mention that? I've attached the
patch.

Regards,

-- 
Masahiko Sawada
Amazon Web Services: https://aws.amazon.com
Attachment

pgsql-hackers by date:

Previous
From: Kyotaro Horiguchi
Date:
Subject: Re: ProcessStartupPacket(): database_name and user_name truncation
Next
From: Masahiko Sawada
Date:
Subject: Performance degradation on concurrent COPY into a single relation in PG16.