Thread: Subscribe to mailing list - General Question
pg_restore: creating TABLE "public.queue_context"
pg_restore: creating SEQUENCE "public.queue_context_id_seq"
pg_restore: while PROCESSING TOC:
pg_restore: from TOC entry 200; 1259 <NUMBER> SEQUENCE queue_context_id_seq sindhu.selvaraj
pg_restore: error: could not execute query: ERROR: unexpected request for new relfilenode in binary upgrade mode
Command was:
-- For binary upgrade, must preserve pg_class oids and relfilenodes
SELECT pg_catalog.binary_upgrade_set_next_heap_pg_class_oid('<NUMBER>'::pg_catalog.oid);
SELECT pg_catalog.binary_upgrade_set_next_heap_relfilenode('<NUMBER>'::pg_catalog.oid);
ALTER TABLE "public"."queue_context" ALTER COLUMN "id" ADD GENERATED BY DEFAULT AS IDENTITY (
SEQUENCE NAME "public"."queue_context_id_seq"
START WITH 1
INCREMENT BY 1
NO MINVALUE
NO MAXVALUE
CACHE 1
);
ALTER SEQUENCE "public"."queue_context_id_seq" SET LOGGED;
This has been spotted in local postgres installed in MAC as well as in AWS RDS.
We had to change the unlogged table to logged and then upgrade.
I am reporting this as a bug. Please keep us updated.
Regards,
Sindhu
SINDHU SELVARAJ
POSTGRESQL DBA
STARLING BANK
On 8/1/24 20:53, Sindhu Selvaraj wrote: > In 15.7 and 16.3 Release Notes, I found a change to an unlogged table's > sequence. > > This has been spotted in local postgres installed in MAC as well as in > AWS RDS. > > We had to change the unlogged table to logged and then upgrade. > > I am reporting this as a bug. Please keep us updated. That should be done here: https://www.postgresql.org/account/submitbug/ FYI, you will need to set up a community account to do that. > > > Regards, > > Sindhu > > SB Logo > > SINDHU SELVARAJ > > POSTGRESQL DBA > > STARLING BANK > > -- Adrian Klaver adrian.klaver@aklaver.com
Adrian Klaver <adrian.klaver@aklaver.com> writes: > On 8/1/24 20:53, Sindhu Selvaraj wrote: >> I am reporting this as a bug. Please keep us updated. > That should be done here: > https://www.postgresql.org/account/submitbug/ > FYI, you will need to set up a community account to do that. I think this is the same thing that was reported yesterday: https://www.postgresql.org/message-id/flat/18562-46a7ee9a7b1ee153%40postgresql.org regards, tom lane