AWS Graviton EC2 Reader instance returns an empty result

[malikmuhammad1]

writer: r5.large standby: r6g.large

step1: writer

CREATE EXTENSION pg_bigm; CREATE INDEX ix_t1_content ON t1 using GIN (content gin_bigm_ops);

insert into t1 (col1, col2, content) SELECT gs10, gs20, concat(md5(random()::text)) AS random_string FROM generate_series(1, 1) AS gs;

update t1 set content = concat(content,'가나다') where id = 1;

rdsadmin=# select * from t1 where content like '%가나다%'; id | col1 | col2 | content
----+------+------+---------------------------------------- 1 | 10 | 20 | 7329992bb1dc5fd43140f6c596cd035c가나다 (1 row)

step2: standby reader

rdsadmin=# select * from t1 where content like '%가나다%'; id | col1 | col2 | content ----+------+------+--------- (0 rows)

rdsadmin=# select * from t1 where content like '%bb1dc5fd431%'; id | col1 | col2 | content
----+------+------+---------------------------------------- 1 | 10 | 20 | 7329992bb1dc5fd43140f6c596cd035c가나다 (1 row)

[ardentperf]

i think this repo is a mirror, afaik it's not monitored. this particular issue was discussed at https://osdn.net/projects/pgbigm/lists/archive/hackers/2024-February/000370.html

[MasaoFujii]

This GitHub page is now the official site for pg_bigm. Let's discuss things here.

The same issue was reported and discussed on pgsql-hackers. It's best to wait for a consensus there, and then update pg_bigm following how pg_trgm resolves the issue. https://www.postgresql.org/message-id/CB11ADBC-0C3F-4FE0-A678-666EE80CBB07@amazon.com