On Thu, Jan 7, 2021 at 2:55 PM PG Bug reporting form
<noreply@postgresql.org> wrote:
>
> The following bug has been logged on the website:
>
> Bug reference: 16812
> Logged by: Mayur B.
> Email address: mayur555b@protonmail.com
> PostgreSQL version: 12.3
> Operating system: Ubuntu 16.04.6 LTS
> Description:
>
> Hi,
> We started receiving the logical decoding error :
> ERROR: could not map filenode "base/16437/140990927" to relation OID
>
> Database is PG 12.3 and Ubuntu 16.04.6 LTS. There is no "vacuum full" or
> CLUSTER happening. What could be other sources of this error?
>
It is not clear to me how else this error can happen. However, I think
this can happen due to some re-write of mapped relations as we don't
maintain historic-view for mapped relations. Having said that, as far
as I understand this shouldn't cause any problem because we anyway
don't decode updates to catalog relations and we would have anyway
skipped this operation. I am not sure maybe this could have been a LOG
instead of ERROR.
One way to figure what is going on here is to add a LOG message in
apply_map_update to see the change relationId and then we might be
able to track which exact operation has changed this. The other
possibility could be to use pg_waldump to figure out the WAL record
which leads to this error (maybe with the help of LSN, we can identify
that).
--
With Regards,
Amit Kapila.