pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
BUG #16812: Logical decoding error
5+ messages / 3 participants
[nested] [flat]

* BUG #16812: Logical decoding error
@ 2021-01-07 08:57  PG Bug reporting form <noreply@postgresql.org>
  0 siblings, 2 replies; 5+ messages in thread

From: PG Bug reporting form @ 2021-01-07 08:57 UTC (permalink / raw)
  To: pgsql-bugs@lists.postgresql.org; +Cc: mayur555b@protonmail.com

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?

Thanks



^ permalink  raw  reply  [nested|flat] 5+ messages in thread

* Re: BUG #16812: Logical decoding error
@ 2021-01-07 11:15  mayur <mayur555b@protonmail.com>
  parent: PG Bug reporting form <noreply@postgresql.org>
  1 sibling, 0 replies; 5+ messages in thread

From: mayur @ 2021-01-07 11:15 UTC (permalink / raw)
  To: mayur555b@protonmail.com <mayur555b@protonmail.com>; pgsql-bugs@lists.postgresql.org <pgsql-bugs@lists.postgresql.org>

Sorry, Operating system is Ubuntu 18.04. We are using pipelinewise to consume wal stream and replicate tables to snowflake. YML config file consist of large number of tables so it is difficult to figure out exact table quickly.

Documentation about pipelinewise
https://transferwise.github.io/pipelinewise/


Sent with ProtonMail Secure Email.

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Thursday, 7 January 2021 10:57, 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?
>
> Thanks







^ permalink  raw  reply  [nested|flat] 5+ messages in thread

* Re: BUG #16812: Logical decoding error
@ 2021-01-12 05:08  Amit Kapila <amit.kapila16@gmail.com>
  parent: PG Bug reporting form <noreply@postgresql.org>
  1 sibling, 1 reply; 5+ messages in thread

From: Amit Kapila @ 2021-01-12 05:08 UTC (permalink / raw)
  To: mayur555b@protonmail.com, PostgreSQL mailing lists <pgsql-bugs@lists.postgresql.org>

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.





^ permalink  raw  reply  [nested|flat] 5+ messages in thread

* Re: BUG #16812: Logical decoding error
@ 2021-01-13 08:35  mayur <mayur555b@protonmail.com>
  parent: Amit Kapila <amit.kapila16@gmail.com>
  0 siblings, 1 reply; 5+ messages in thread

From: mayur @ 2021-01-13 08:35 UTC (permalink / raw)
  To: Amit Kapila <amit.kapila16@gmail.com>; +Cc: mayur555b@protonmail.com <mayur555b@protonmail.com>; PostgreSQL mailing lists <pgsql-bugs@lists.postgresql.org>

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.kapila16@gmail.com> wrote:

> 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.







^ permalink  raw  reply  [nested|flat] 5+ messages in thread

* Re: BUG #16812: Logical decoding error
@ 2021-01-15 03:59  Amit Kapila <amit.kapila16@gmail.com>
  parent: mayur <mayur555b@protonmail.com>
  0 siblings, 0 replies; 5+ messages in thread

From: Amit Kapila @ 2021-01-15 03:59 UTC (permalink / raw)
  To: mayur <mayur555b@protonmail.com>; +Cc: PostgreSQL mailing lists <pgsql-bugs@lists.postgresql.org>

On Wed, Jan 13, 2021 at 2:05 PM mayur <mayur555b@protonmail.com> wrote:
>
> Thanks. This was happening because Patroni was removing inactive replication slot.
>

It is not apparent to me how removing the inactive replication slot by
Patroni causes this error. Can you please explain what's going on?

-- 
With Regards,
Amit Kapila.





^ permalink  raw  reply  [nested|flat] 5+ messages in thread


end of thread, other threads:[~2021-01-15 03:59 UTC | newest]

Thread overview: 5+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2021-01-07 08:57 BUG #16812: Logical decoding error PG Bug reporting form <noreply@postgresql.org>
2021-01-07 11:15 ` mayur <mayur555b@protonmail.com>
2021-01-12 05:08 ` Amit Kapila <amit.kapila16@gmail.com>
2021-01-13 08:35   ` mayur <mayur555b@protonmail.com>
2021-01-15 03:59     ` Amit Kapila <amit.kapila16@gmail.com>

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox