Re: logical decoding bug: segfault in ReorderBufferToastReplace() - Mailing list pgsql-bugs

From Andres Freund
Subject Re: logical decoding bug: segfault in ReorderBufferToastReplace()
Date
Msg-id 20191211172101.k55jz364chv77ewh@alap3.anarazel.de
Whole thread Raw
In response to Re: logical decoding bug: segfault in ReorderBufferToastReplace()  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
Hi,

On 2019-12-11 12:11:03 -0500, Tom Lane wrote:
> I don't think you can make that conclusion.  Perhaps the table once
> needed a toast table because of some wide column that got dropped;
> if so, it'd still have one.  It'd be safer to look at
> pg_class.reltoastrelid to verify existence (or not) of the toast relation.

That was checked in the email I was responding to.


> It strikes me that there could easily be cases where a publisher table
> has a toast relation and a subscriber's doesn't ... maybe this code
> isn't expecting that?

This code is all running on the publisher side, so I don't think it
could matter.

Greetings,

Andres Freund



pgsql-bugs by date:

Previous
From: Robert Haas
Date:
Subject: Re: logical decoding bug: segfault in ReorderBufferToastReplace()
Next
From: Roman Cervenak
Date:
Subject: Re: Memory leak (possibly connected to postgis) leading to server crash