On Thu, Jul 11, 2019 at 09:28:00PM -0400, Steve Singer wrote:
> On Thu, 11 Jul 2019, David Fetter wrote:
> 
> > On Thu, Jul 11, 2019 at 01:10:43PM -0400, steve at ssinger.info steve at ssinger.info wrote:
> > > 14GB isn't very big.
> > > Any idea what is happening?
> > 
> > Nope, and that's why I wrote here.
> > 
> > > Are there any locks on the table (on the origin or replica) that could be preventing this?
> > 
> > Not that I can see.
> > 
> > > What is in the slon log, for the slon for the replica.
> > 
> > Nothing in sl_log_1 or sl_log_2 on the either the origin or the replica, nothing in
> > /var/log/slony1/ on either the origin or the replica.
> 
> 'nothing' in the log makes me think that your looking at the wrong log file,
> or logging isn't working.
> 
> I would expect to see something like the following when it starts to copy a
> table

This is a little embarrassing, but I checked things that I thought
couldn't matter, and it turns out that the database had had
statement_timeout set low enough that the initial sync would always
fail.

Sheepishly,
David.
-- 
David Fetter <david(at)fetter(dot)org> http://fetter.org/
Phone: +1 415 235 3778

Remember to vote!
Consider donating to Postgres: http://www.postgresql.org/about/donate