Re: Reject COPY TO of unlogged relations during recovery

From: Jim Jones <jim(dot)jones(at)uni-muenster(dot)de>
To: Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>
Cc: Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Reject COPY TO of unlogged relations during recovery
Date: 2026-10-17 11:01:29
Message-ID: 73c93dbb-bf70-4c02-b7bf-b81e95ee65be@uni-muenster.de
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 16/10/2026 20:11, Masahiko Sawada wrote:
> While I agree that we can report a proper error message instead at
> these places, I think we need to note that pageinspect's check for
> init fork should work even on the standby.

Ok, I will create a followup thread only with the contrib fixes and take
this into account for pageinspect. Thanks.
> Also, currtid2() seems to have the same issue.

Yeah, I can reproduce the same issue in currtid2().

psql (20devel)
Type "help" for help.

postgres=# SELECT currtid2('t', '(0,1)'::tid);
ERROR: could not open file "base/5/16384": No such file or directory

0002 attached adds a check to report an error message for it.

Thanks!

Best, Jim

Attachment Content-Type Size
v3-0001-Reject-COPY-TO-of-unlogged-tables-during-recovery.patch text/x-patch 4.5 KB
v3-0002-Reject-currtid2-on-unlogged-tables-during-recover.patch text/x-patch 1.9 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Manu 2026-10-17 11:55:29 Re: pg_upgrade stores an invalid datminmxid/relminmxid when the old cluster's newest multixact is 0xFFFFFFFF
Previous Message Alexander Lakhin 2026-10-17 11:00:00 Re: Internal error codes triggered by regression tests and user queries, take 2