Re: BUG #16812: Logical decoding error

From: mayur <mayur555b(at)protonmail(dot)com>
To: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
Cc: "mayur555b(at)protonmail(dot)com" <mayur555b(at)protonmail(dot)com>, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: BUG #16812: Logical decoding error
Date: 2021-01-13 08:35:31
Message-ID: YU299gZUNW-yjPsQVxz72DqmSvJ5weGbstLY7RkZkgqLApZlyEuOEtVZuFI0axSCw6N9NBXYUTee5e9J87imRcFBzN6ZEPPrMa9hZJg3POI=@protonmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Thanks. This was happening because Patroni was removing inactive replication slot.

Sent with ProtonMail Secure Email.

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Tuesday, 12 January 2021 07:06, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> wrote:

> On Thu, Jan 7, 2021 at 2:55 PM PG Bug reporting form
> noreply(at)postgresql(dot)org wrote:
>
> > The following bug has been logged on the website:
> > Bug reference: 16812
> > Logged by: Mayur B.
> > Email address: mayur555b(at)protonmail(dot)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.

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Nikhil Saple 2021-01-13 12:26:55 NO acceptable C compiler found in the $PATH
Previous Message PG Bug reporting form 2021-01-13 07:43:43 BUG #16820: PG will have a deadlock when multiple rows are updated concurrently