Re: [Patch] Use *other* indexes on the subscriber when REPLICA IDENTITY is FULL

Önder Kalacı <onderkalaci@gmail.com>

From: Önder Kalacı <onderkalaci@gmail.com>
To: Amit Kapila <amit.kapila16@gmail.com>
Cc: "Hayato Kuroda (Fujitsu)" <kuroda.hayato@fujitsu.com>, Postgres hackers <pgsql-hackers@lists.postgresql.org>
Date: 2023-07-10T14:13:42Z
Lists: pgsql-hackers
Hi,

I also think so. If this is true, how can we think of supporting
> indexes other than hash like GiST, and SP-GiST as mentioned by you in
> your latest email? As per my understanding if we don't have PK or
> replica identity then after the index scan, we do tuples_equal which
> will fail for GIST or SP-GIST. Am, I missing something?
>

I also don't think we can support anything other than btree, hash and brin
as those lack equality operators.

And, for BRIN, Hayato brought up the amgettuple issue, which is fair. So,
overall, as far as I can see, we can
easily add hash indexes but all others are either very hard to add or not
possible.

I think if someone one day works on supporting primary keys using other
index types, we can use it here :p

Thanks,
Onder

Commits

  1. Allow the use of a hash index on the subscriber during replication.

  2. Allow the use of indexes other than PK and REPLICA IDENTITY on the subscriber.