On Tue, 2025-07-29 at 15:00 +0800, yexiu-glory wrote:
> The approach of adding unique indexes is not suitable for our business.
Well, then I guess that logical replication is not suitable for your business.
Yours,
Laurenz Albe
>>>On Fri, 2025-07-18 at 19:08 +0800, yexiu-glory wrote:
>
>>>I'm facing a problem here: our business requires logical data
replication to other departments,
>>>but at the same time, sensitive fields need to be filtered out.
Therefore,
>>>we used the column filtering function when creating logica
ll column field
Or create Surrogate Primary Key
2.
Use that index as the REPLICA IDENTITY.
Regards
Dinesh Nair
____
From: yexiu-glory
Sent: Friday, July 18, 2025 4:38 PM
To: pgsql-general
Subject: Regarding logical replication issues with PostgreSQL version
On Fri, 2025-07-18 at 19:08 +0800, yexiu-glory wrote:
> I'm facing a problem here: our business requires logical data replication to
> other
> departments, but at the same time, sensitive fields need to be filtered out.
> Therefore, we used the column filtering function when creating logical
> re
I'm facing a problem here: our business requires logical data replication to
other departments, but at the same time, sensitive fields need to be filtered
out. Therefore, we used the column filtering function when creating logical
replication. If we use `alter table table1 replica identity defau
Yeah it is latest.
I am using Postgres 9.6.
Thanks!
Sudhakaran
On Tue, 15 Jun 2021 at 10:42 PM, Mateusz Henicz
wrote:
> Do you have "recovery_target_timeline=latest" configured in your
> recovery.conf or postgresql.conf? Depending on the version you are using,
> up to 11 recovery.conf and pos
At Tue, 15 Jun 2021 07:05:07 -0700 (MST), "email2ssk...@gmail.com"
wrote in
> Even I have this problem when I had to recover the database failed
> switchover.
> This is error is new primary server.
>
> < 2021-06-15 16:05:02.480 CEST > ERROR: requested starting point
> AF/7D00 on timeline
Do you have "recovery_target_timeline=latest" configured in your
recovery.conf or postgresql.conf? Depending on the version you are using,
up to 11 recovery.conf and postgresql.conf 12+.
Cheers,
Mateusz
wt., 15 cze 2021, 22:05 użytkownik email2ssk...@gmail.com <
email2ssk...@gmail.com> napisał:
Even I have this problem when I had to recover the database failed
switchover.
This is error is new primary server.
< 2021-06-15 16:05:02.480 CEST > ERROR: requested starting point
AF/7D00 on timeline 1 is not in this server's history
< 2021-06-15 16:05:02.480 CEST > DETAIL: This server's h
Hello,
I've created synchronous replication between Primary and Secondary server and
put pacemaker + PAF over. Client is doing some stress tests (switching nodes,
disabling particular node, etc) and it's second time when this kind of problem
occoures :
2020-12-18 14:03:46.658 CET [unknown] [
On Mon, 23 Sep 2019, 00:46 Shital A, wrote:
>
> Hello,
>
> We have setup active-passive cluster using streaming replication on Rhe
> 7.5. We are testing pacemaker for automated failover.
> We are seeing below issues with the setup :
>
> 1. When a failoveris triggered when data is being added to t
Hello,
We have setup active-passive cluster using streaming replication on Rhe
7.5. We are testing pacemaker for automated failover.
We are seeing below issues with the setup :
1. When a failoveris triggered when data is being added to the primary by
killing primary (killall -9 postgres), the sta
On 28/9/18 1:50 μ.μ., bhargav kamineni wrote:
Ee are using 9.5 version, slot option -s is not available ,can I go with -X
stream option ?
-S is intended when you plan to use the backup as a hot standby, when you must
use the same replication slot.
If you plan to use the backup as a stand alone
Ee are using 9.5 version, slot option -s is not available ,can I go with -X
stream option ?
On Fri 28 Sep, 2018, 12:01 PM Laurenz Albe,
wrote:
> bhargav kamineni wrote:
> > Hi Team,
> >
> > I have configured replication using slot ,But it failed by throwing the
> > ERROR pg_basebackup: could n
bhargav kamineni wrote:
> Hi Team,
>
> I have configured replication using slot ,But it failed by throwing the
> ERROR pg_basebackup: could not get transaction log end position from server:
> ERROR: requested WAL segment 00012C9D0085 has already been
> removed ,
> which is unexpec
On 28/9/18 9:00 π.μ., bhargav kamineni wrote:
Hi Team,
I have configured replication using slot ,But it failed by throwing the ERROR /pg_basebackup: could not get transaction log end position from server: ERROR: requested WAL segment
00012C9D0085 has already been removed /, which i
Hi Team,
I have configured replication using slot ,But it failed by throwing the
ERROR *pg_basebackup: could not get transaction log end position from
server: ERROR: requested WAL segment 00012C9D0085 has already
been removed *, which is unexpected because i have created the slot on
17 matches
Mail list logo
