mirror of
https://github.com/postgres/postgres.git
synced 2026-10-23 13:29:09 +03:00
1e707d3256
Unlogged tables have no data on a standby, so reading one there must fail. SELECT and COPY (SELECT ...) TO already report a clear error, but COPY with a table name read the table directly and failed with a low-level error instead: ERROR: could not open file "base/5/16384": No such file or directory Check for this case in COPY TO and report the same error as SELECT. On v19 and later, also check each partition when copying from a partitioned table, so that an unlogged partition is reported too. Backpatch to all supported versions, since the low-level error looks like data corruption. Author: Jim Jones <jim.jones@uni-muenster.de> Reviewed-by: Zsolt Parragi <zsolt.parragi@percona.com> Reviewed-by: Masahiko Sawada <sawada.mshk@gmail.com> Discussion: https://postgr.es/m/b6d71815-d362-4579-bf07-73eca01aee6d@uni-muenster.de Backpatch-through: 14