Re: Heavy Logging in Subscriber side when configured LogicalReplication in 10.4

Поиск
Список
Период
Сортировка
От pavan95
Тема Re: Heavy Logging in Subscriber side when configured LogicalReplication in 10.4
Дата
Msg-id 1535792170623-0.post@n3.nabble.com
обсуждение исходный текст
Ответы Re: Heavy Logging in Subscriber side when configured LogicalReplication in 10.4  (pavan95 <pavan.postgresdba@gmail.com>)
Re: Heavy Logging in Subscriber side when configured LogicalReplication in 10.4  (Achilleas Mantzios <achill@matrix.gatewaynet.com>)
Список pgsql-admin
Hi Team,

We have successfully configured and tested Logical Replication between
Publisher and Subscriber. But on the Subscriber side we are getting
generated a number of error log files(around 20-30 GB). 

The most common log messages found in the log(/var/log/postgresql/abc.log)
are:
2018-08-26 06:32:09.659 IST [9385] ERROR:  duplicate key value violates
unique constraint "table_pkey"
2018-08-26 06:32:09.637 IST [13919] LOG:  worker process: logical
replication worker for subscription 4858103 sync 189974 (PID 9384) exited
with exit code 1
2018-08-26 06:32:09.638 IST [13919] LOG:  worker process: logical
replication worker for subscription 4858103 sync 188985 (PID 9383) exited
with exit code 1


Some 72 lakh times the above errors are occurring. How to prevent this
behaviour? Kindly assist me!!

Thanks in Advance.

Regards,
Pavan






--
Sent from: http://www.postgresql-archive.org/PostgreSQL-admin-f2076596.html


В списке pgsql-admin по дате отправления:

Предыдущее
От: Ron
Дата:
Сообщение: pg_dump and disk full
Следующее
От: pavan95
Дата:
Сообщение: Re: Can we exclude errors of some particular text in Postgres logfile?