Hi,When I tried to update the flush LSN position of the logical replication slot for my 11.3 database, using the command select pg_replication_slot_advance(, )I get the error:user=cdcpsqlsrc,db=db_dsn_test03,app=PostgreSQL JDBC Driver,client=172.24.42.236 DEBUG: failed to increase restart lsn: prop
Hi,I am trying to set the fetch size for my ResultSet to avoid Out of Memory exception. I have created the Statement with ResultSet.TYPE_FORWARD_ONLY, ResultSet.CONCUR_READ_ONLY and ResultSet.HOLD_CURSORS_OVER_COMMIT and I've also disabled auto commit as mentioned in the link Getting results based
Hi,Is there a SQL query or a database parameter setting that I can use from an external application to determine if the PostgreSQL database is on cloud (like on Amazon RDS or IBM cloud) or on a non-cloud on-prem environment?Thanks,Rashmi
feedback mechanism
right?
Thanks,
Rashmi
-"Rashmi V Bharadwaj" wrote: -
To: Andres Freund
From: "Rashmi V Bharadwaj"
Date: 13/03/2019 10:59AM
Cc: pgsql-gene...@postgresql.org
Subject: Re: PostgreSQL logical replication slot LSN values
Hi,
> Well, did you consum
that didn't work. It still gives the WAL segment already removed error.
Could you please suggest a solution for this? Is there a way to set the
restart_lsn and flush_lsn of slot? Or is recreating the slot the only possible
solution?
Thanks,
Rashmi
-----Andres Freund wrote: -
To: Rash
Hi,We have an application that uses the PostgreSQL logical replication API to read the changes made to the PostgreSQL database and applies it to a different database (like Db2 etc). We are using logical replication slots for this. Currently I am facing an issue where the replication slot is pointin
