Re: TRAP: FailedAssertion("!(TransactionIdPrecedesOrEquals
От | Michael Paquier |
---|---|
Тема | Re: TRAP: FailedAssertion("!(TransactionIdPrecedesOrEquals |
Дата | |
Msg-id | CAB7nPqSLXiYV5iBxFF6teH=EKsQx9xFskswMVWWdfMmKL3L0rg@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: TRAP: FailedAssertion("!(TransactionIdPrecedesOrEquals (Erik Rijkers <er@xs4all.nl>) |
Ответы |
Re: TRAP: FailedAssertion("!(TransactionIdPrecedesOrEquals
|
Список | pgsql-hackers |
On Wed, Dec 20, 2017 at 7:46 AM, Erik Rijkers <er@xs4all.nl> wrote: > Sorry, that was probably too terse, I should explain that a little. > > After initing 50 instances, I set up and run a pgbench session in the master > session; the pgbench lines are: > > init: pgbench --port=6515 --quiet --initialize --scale=1 postgres > run: pgbench -M prepared -c 16 -j 8 -T 1 -P 1 -n postgres -- scale 1 > > the other instances then catch up. The whole takes 5 minutes or so > > I vary scale, duration, and number of instances. I haven't had it fail in > this way yet but I mostly tried with lower number of instances (up to 25 or > so). Hm. Are you saying that it takes at least 50 cascading instances to see the problem you are seeing? And that you are not seeing any problems with a lower number of cascading instances? Are you enabling hot_standby_feedback? -- Michael
В списке pgsql-hackers по дате отправления: