From: | PG Bug reporting form <noreply(at)postgresql(dot)org> |
---|---|
To: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
Cc: | jason(dot)chentj(at)homecredit(dot)cn |
Subject: | BUG #18540: Does PG16 standby database support function pg_replication_origin_advance? |
Date: | 2024-07-15 08:28:26 |
Message-ID: | 18540-eb48b78bd306c618@postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
The following bug has been logged on the website:
Bug reference: 18540
Logged by: Does PG16 standby database support function pg_replication_origin_advance?
Email address: jason(dot)chentj(at)homecredit(dot)cn
PostgreSQL version: 16.1
Operating system: Red Hat Enterprise Linux Server release 7.9
Description:
Hi Guys,
am testing the PG 16 VERSION standby database replicate slot function. when
I issue below command to move the offset for replicate slot on standby
database got below error:
db_plumc=# select
pg_replication_origin_advance('standbyslot','5EE/5D1B13F8'::pg_lsn);
ERROR: cannot manipulate replication origins during recovery
Seems the function pg_replication_origin_advance is not supported running on
standby instance. It there any workaround for it?
Thanks
Jason
From | Date | Subject | |
---|---|---|---|
Next Message | PG Bug reporting form | 2024-07-15 10:00:01 | BUG #18541: Reattaching a partition referenced by a foreign key fails with an error |
Previous Message | Tom Lane | 2024-07-14 17:30:55 | Re: BUG #18536: Using WITH inside WITH RECURSIVE triggers a "shouldn't happen" error |