On Wed, Dec 1, 2021 at 5:56 PM Marcos Pegoraro wrote:
>
>> I have an issue with logical replication after Postgresql upgrade from
>> 13 to 14 (upgraded subscriber only using pg_upgrade_cluster -m link 13
>> main). After upgrade all subscriptions were disabled so I have enabled
>> them and replicat
I think there are some bugs in Posgresql logical replication upgrade.
Because dropping and recreating subscriptions with manual
synchronization has solved the problem for me. But it is not the
correct way, IMHO.
Sergey Belyashov
ср, 1 дек. 2021 г. в 15:26, Marcos Pegoraro :
>
>
>> I have an issue
> I have an issue with logical replication after Postgresql upgrade from
> 13 to 14 (upgraded subscriber only using pg_upgrade_cluster -m link 13
> main). After upgrade all subscriptions were disabled so I have enabled
> them and replication workers successfully started.
> pg_stat_subscription cont
I have an issue with logical replication after Postgresql upgrade from
13 to 14 (upgraded subscriber only using pg_upgrade_cluster -m link 13
main). After upgrade all subscriptions were disabled so I have enabled
them and replication workers successfully started.
pg_stat_subscription contains list
hello Kyotaro,
thx for you feedback and clarification.
Le ven. 31 juil. 2020 à 02:13, Kyotaro Horiguchi
a écrit :
> Hi,
>
> At Thu, 30 Jul 2020 14:54:08 +0100, FOUTE K. Jaurès
> wrote in
> > Hi everyone,
> >
> > Situation:
> >
> >- A Master Database on the HQ
> >- i make a dump of th
Hi,
At Thu, 30 Jul 2020 14:54:08 +0100, FOUTE K. Jaurès
wrote in
> Hi everyone,
>
> Situation:
>
>- A Master Database on the HQ
>- i make a dump of the master database to the Subdivision Server
>- I create à Publication like: CREATE PUBLICATION
>iNOV_MasterData_Table_Pub FOR T
Hi everyone,
Situation:
- A Master Database on the HQ
- i make a dump of the master database to the Subdivision Server
- I create à Publication like: CREATE PUBLICATION
iNOV_MasterData_Table_Pub FOR TABLE M_Product; On the Master Database
- On the Subdivision Server, I create a Sub
My table has a primary key. In addition, this is an initial load issue where
the replication identity should not matter.
-Original Message-
From: Michael Lewis
To: Donzell White
Cc: pgsql-general
Sent: Tue, Jun 30, 2020 1:05 pm
Subject: Re: Logical Replication Issue
Per the release
Per the release notes, there are some enhancements to logical replication
that came after 11.5 like 11.8 particularly related to replication identity
full. Do you have a primary key or unique index that is being used for the
replication identity?
Hi,
I have set up logical replication from an AWS RDS instance to a postgreSQL
database on an EC2 instance. I am getting an “out of memory” error during the
initial for one of the tables. I have include a snippet of the error at the
bottom of this email. The snippet below repeats every four or e
Hello,
we are using logical replication from PostgreSQL 10.8 (Ubuntu
10.8-1.pgdg14.04+1) to PostgreSQL 11.3 (Ubuntu 11.3-1.pgdg18.04+1). Thre
are 1305 replicated tables within 3 schemas. The tables are from small
almost static lookup tables to larger tables up to ~40GB holding 44
millions of row
Hello,
I've found an issue with logical replication causing
1) large memory allocation by wal sender process (RSS 60GB)
2) large amount of "xid" files in $PGDATA/pg_replslot/
directory - seems to be amount of rows handled by trigger + few more
Having several millions of files in a single director
12 matches
Mail list logo