pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Ondřej Jirman <ienieghapheoghaiwida@xff.cz>
To: Tomas Vondra <tomas.vondra@2ndquadrant.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #16129: Segfault in tts_virtual_materialize in logical replication worker
Date: Fri, 22 Nov 2019 18:40:03 +0100
Message-ID: <20191122174003.xyaixb6iwbvtyplp@core.my.home> (raw)
In-Reply-To: <20191122161248.qnzeoh6t7fvg5wl3@development>
References: <20191121161502.xfiy65i3cm6adscr@core.my.home>
	<20191121165752.dffge6bh756xlfdg@development>
	<20191121173555.midj6vp4dmiiqs24@core.my.home>
	<20191121185844.6qsqhwzzuhu3fpsg@core.my.home>
	<20191121214115.3tgefmvkmrzaim74@development>
	<20191121220854.ebdzjtloel56sfwu@development>
	<20191122003626.ydgwvjfx363blgip@core.my.home>
	<16189.1574383534@sss.pgh.pa.us>
	<20191122005401.bkdpmtqwuu6mvnyg@core.my.home>
	<20191122161248.qnzeoh6t7fvg5wl3@development>

On Fri, Nov 22, 2019 at 05:12:48PM +0100, Tomas Vondra wrote:
> On Fri, Nov 22, 2019 at 01:54:01AM +0100, Ondřej Jirman wrote:
> > On Thu, Nov 21, 2019 at 07:45:34PM -0500, Tom Lane wrote:
> > > =?utf-8?Q?Ond=C5=99ej?= Jirman <ienieghapheoghaiwida@xff.cz> writes:
> > > > On Thu, Nov 21, 2019 at 11:08:54PM +0100, Tomas Vondra wrote:
> > > >> 1) Print newtup.values and newtup.changed matches, so that we can check
> > > >> it contains the tuple I shared before? There should be 8 elements in
> > > >> each, with 'values' being values formatted as text, and 'changed' being
> > > >> flags which values were updated.
> > > 
> > > > newtup.changed
> > > 
> > > > {true, true, false, true, true, true, true, true, false <repeats 1656 times>}
> > > 
> > > So column 3 is not getting replaced.  That seems to jibe with my
> > > theory that slot_modify_cstrings is failing to handle that case
> > > correctly.  Can you try applying the patch I posted and see if
> > > it fixes the issue for you?
> > 
> > With the patch the replication resumes, without a crash.
> > 
> > confirmed_flush_lsn is now same for all my replication slots.
> > 
> > thank you and regards,
> 
> Can you show us the attribute list as defined in the system, including
> e.g. dropped columns? That is, something like
> 
>   SELECT attnum, attname, atttypid FROM pg_attribute
>    WHERE attrelid = 'public.videos'::regclass;
> 
> both from the published and subscriber.

I don't think there were any dropped columns and replica was always created
by schema copy + subscribe with copy_data=true. Anyway, the original database is
gone now (on both ends), so I can't get any more info.

regards,
	o.

> regards
> 
> -- 
> Tomas Vondra                  http://www.2ndQuadrant.com
> PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services





view thread (40+ messages)

Message-ID: <20191122174003.xyaixb6iwbvtyplp@core.my.home>
Permalink:  ../20191122174003.xyaixb6iwbvtyplp@core.my.home/
Also on:    postgresql.org/message-id/20191122174003.xyaixb6iwbvtyplp@core.my.home

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-bugs@postgresql.org
  Cc: ienieghapheoghaiwida@xff.cz, tomas.vondra@2ndquadrant.com, tgl@sss.pgh.pa.us, pgsql-bugs@lists.postgresql.org
  Subject: Re: BUG #16129: Segfault in tts_virtual_materialize in logical replication worker
  In-Reply-To: <20191122174003.xyaixb6iwbvtyplp@core.my.home>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

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