On Wed, Apr 8, 2020 at 11:07 PM Amit Langote <amitlangote09@gmail.com> wrote:
> On Wed, Apr 8, 2020 at 9:21 PM Peter Eisentraut
> <peter.eisentraut@2ndquadrant.com> wrote:
> > On 2020-04-08 13:16, Amit Langote wrote:
> > > prion seems to have failed:
> > > https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=prion&dt=2020-04-08%2009%3A53%3A13
> >
> > This comes from -DRELCACHE_FORCE_RELEASE.
>
> I'm seeing some funny stuff on such a build locally too, although
> haven't been able to make sense of it yet.
So, I see the following repeated in the publisher's log
(013_partition.pl) until PostgresNode.pm times out:
sub_viaroot ERROR: number of columns (2601) exceeds limit (1664)
sub_viaroot CONTEXT: slot "sub_viaroot", output plugin "pgoutput", in
the change callback, associated LSN 0/1621010
causing the tests introduced by this last commit to stall.
Just before where the above starts repeating is this:
sub_viaroot_16479_sync_16455 LOG: starting logical decoding for slot
"sub_viaroot_16479_sync_16455"
sub_viaroot_16479_sync_16455 DETAIL: Streaming transactions
committing after 0/1620A40, reading WAL from 0/1620A08.
sub_viaroot_16479_sync_16455 LOG: logical decoding found consistent
point at 0/1620A08
sub_viaroot_16479_sync_16455 DETAIL: There are no running transactions.
sub_viaroot_16479_sync_16470 LOG: statement: COPY public.tab3_1 TO STDOUT
sub_viaroot_16479_sync_16470 LOG: statement: COMMIT
Same thing for the other subscriber sub2.
--
Amit Langote
EnterpriseDB: http://www.enterprisedb.com
