Re: Right way to restore logical replication

Thanks for reply!It makes sense now why that happened and what to do in case of emergency 09.02.2021, 10:01, "Kyotaro Horiguchi" :At Mon, 08 Feb 2021 22:42:21 +0700, Игорь Выскорко wrote in Hi, community! Unfortunately can't find answer in docs and google. Hope only for yo

Re: Right way to restore logical replication

At Mon, 08 Feb 2021 22:42:21 +0700, Игорь Выскорко wrote in > Hi, community! > Unfortunately can't find answer in docs and google. Hope only for you) > [local]:5433 postgres@postgres=# drop publication pub ; > DROP PUBLICATION > Time: 3,793 ms > > [local]:5433 postgres@postgres=# insert into tb

Re: identifier will be truncated

Hi Joao, > On 08. Feb, 2021, at 17:39, Joao Miguel Ferreira > wrote: > > NOTICE: identifier > "y1972_1004_vat_periodic_declaration_suppliers_lines_dupl_c24_liq" will be > truncated to "y1972_1004_vat_periodic_declaration_suppliers_lines_dupl_c24_li" > > Please advise on what I should do abo

Re: identifier will be truncated

On 2/8/21 8:39 AM, Joao Miguel Ferreira wrote: Hello all, I'm running unit/integration tests on a pg based application. I recently started getting the following indication on the test suite pg client: NOTICE:  identifier "y1972_1004_vat_periodic_declaration_suppliers_lines_dupl_c24_liq" will

identifier will be truncated

Hello all, I'm running unit/integration tests on a pg based application. I recently started getting the following indication on the test suite pg client: NOTICE: identifier "y1972_1004_vat_periodic_declaration_suppliers_lines_dupl_c24_liq" will be truncated to "y1972_1004_vat_periodic_declaratio

Right way to restore logical replication

Hi, community!Unfortunately can't find answer in docs and google. Hope only for you)Have running 2 postgres locally: :5433 - postgres 11 as master:5434 - postgres 12 as slave Creating basic setup for testing:[local]:5433 postgres@postgres=# create table tbl(id serial, d text, primary key(id));CREAT