Re: Logical Replication WIP

Поиск
Список
Период
Сортировка
От Petr Jelinek
Тема Re: Logical Replication WIP
Дата
Msg-id 4c868c4c-65c5-19f0-51aa-3e9b4d86ba01@2ndquadrant.com
обсуждение исходный текст
Ответ на Re: Logical Replication WIP  (Erik Rijkers <er@xs4all.nl>)
Список pgsql-hackers
Hi,

On 07/09/16 14:10, Erik Rijkers wrote:
> On 2016-08-31 22:51, Petr Jelinek wrote:
>>
>> and one more version with bug fixes, improved code docs and couple
>
>
> I am not able to get the replication to work. Would you (or anyone) be
> so kind to point out what I am doing wrong?
>
> Patches applied, compiled, make-checked, installed OK.
>
> I have 2 copies compiled and installed,  logical_replication and
> logical_replication2, to be publisher and subscriber, ports 6972 and
> 6973 respectively.
>
>
> Logfile subscriber-side:
> [...]
> 2016-09-07 13:47:44.441 CEST 21997 LOG:  MultiXact member wraparound
> protections are now enabled
> 2016-09-07 13:47:44.528 CEST 21986 LOG:  database system is ready to
> accept connections
> 2016-09-07 13:47:44.529 CEST 22002 LOG:  logical replication launcher
> started
> 2016-09-07 13:52:11.319 CEST 22143 LOG:  logical replication apply for
> subscription sub1 started
> 2016-09-07 13:53:47.010 CEST 22143 ERROR:  could not open relation with
> OID 0
> 2016-09-07 13:53:47.012 CEST 21986 LOG:  worker process: logical
> replication worker 24048 (PID 22143) exited with exit code 1
> 2016-09-07 13:53:47.018 CEST 22184 LOG:  logical replication apply for
> subscription sub1 started
> 2016-09-07 13:53:47.028 CEST 22184 ERROR:  could not open relation with
> OID 0
> 2016-09-07 13:53:47.030 CEST 21986 LOG:  worker process: logical
> replication worker 24048 (PID 22184) exited with exit code 1
> 2016-09-07 13:53:52.041 CEST 22187 LOG:  logical replication apply for
> subscription sub1 started
> 2016-09-07 13:53:52.045 CEST 22187 ERROR:  could not open relation with
> OID 0
> 2016-09-07 13:53:52.046 CEST 21986 LOG:  worker process: logical
> replication worker 24048 (PID 22187) exited with exit code 1
> (repeat every few seconds)
>
>

It means the tables don't exist on subscriber. I added check and proper 
error message in my local dev branch, it will be part of the next update.

--   Petr Jelinek                  http://www.2ndQuadrant.com/  PostgreSQL Development, 24x7 Support, Training &
Services



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

Предыдущее
От: Aleksander Alekseev
Дата:
Сообщение: Re: Patch: Implement failover on libpq connect level.
Следующее
От: Pavan Deolasee
Дата:
Сообщение: Re: Vacuum: allow usage of more than 1GB of work mem