Re: BUG #16129: Segfault in tts_virtual_materialize in logical replication worker

On Thu, Nov 21, 2019 at 04:57:07PM +0100, Ondřej Jirman wrote:
>
> Maybe it has something to do with my upgrade method. I dumped/restored
> the replica with pg_dumpall, and then just proceded to enable subscription
> and refresh publication with (copy_data=false) for all my subscriptions.

OTOH, it may not. There are 2 more databases replicated the same way from
the same database cluster, and they don't crash the replica server, and
continue replicating. The one of the other databases also has bytea columns in
some of the tables.

It really just seems related to the machine restart (a regular one) that I did
on the primary, minutes later replica crashed, and kept crashing ever since
whenever connecting to the primary for the hometv database.

So maybe something's wrong with the replica database (maybe because the
connection got killed by the walsender at unfortunate time), rather than the
original database, because I can replicate the original DB afresh into a new copy
just fine and other databases continue replicating just fine if I disable
the crashing subscription.

regards,
o.

> Now, I've tried to start fresh and replicate from the primary "hometv" database
> into a new l5_hometv2 on my crashing 12.1 server and it replicates fine, no
> crashes. Anyway even in this fresh replicated database, there's no REPLICA
> IDENTITY in the \d+ output.
>
> I don't have multiple postgresql installations on the host. There's only
> a difference between primary version 11.5 (ARMv7) and replica 12.1 (x86_64).
>
> regards,
> o.
>
> > regards
> >
> > --
> > Tomas Vondra http://www.2ndQuadrant.com
> > PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services