From: | Henry Hinze <henry(dot)hinze(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Re: BUG #16643: PG13 - Logical replication - initial startup never finishes and gets stuck in startup loop |
Date: | 2020-09-30 06:34:33 |
Message-ID: | CAJs-y_-6c+OH=3ofq7SsANZ7JOpy-yUW37WmAD6XhFi3_csN=w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Hi Tom,
thanks for your reply!
For my comparison test of PG 12 and 13 I did not change any default setting
except wal_level.
But I also did some tests and increased wal_keep_size
and max_slot_wal_keep_size to 1GB. And I set wal_sender_timeout to 1h but
without success. The setup works in PG 13 only with a small amount of data.
Best,
Henry
Am Di., 29. Sept. 2020 um 22:09 Uhr schrieb Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
> PG Bug reporting form <noreply(at)postgresql(dot)org> writes:
> > The following setup of logical replication for one table works nicely
> with
> > PG 12.4. In PG 13.0 the initial startup never finishes. Instead it starts
> > over and over again.
>
> It kinda looks like something is timing out before it's managed to
> catch up with the (rather large) initial state of table t. What
> non-default replication settings are you using?
>
> regards, tom lane
>
--
Diplominformatiker Henry Hinze
Dietzgenstraße 75
13156 Berlin
Tel: +49 - 177 - 3160621
USt-ID: DE306639264
From | Date | Subject | |
---|---|---|---|
Next Message | PG Bug reporting form | 2020-09-30 06:42:19 | BUG #16646: systemctl stop postgresql-12 stuck |
Previous Message | rob stone | 2020-09-30 06:01:23 | Incorrect version of initdb |