Re: Zero Downtime Upgrade

You might try ogr2ogr - it can do postgres to postgres as easily as Postgres to something else and I think can do databases, schemas or individual tables in a single command Though your original stays up, I'd recommend not writing to it while being copied... Brent Wood On Tuesday, Nove

Zero Downtime Upgrade

Hi Group What tools exist besides bucardo, londiste and rubyrep for logical replication to do a zero/near zero downtime upgrade? Thanks in advance

Re: Question: Is it possible to get the new xlog position after query execution?

> On Nov 8, 2021, at 11:47, Oleg Serov wrote: > I'm sorry, when I mean users, I mean application end-user (e.g. > j...@doe.com), not the postgres role. You can also set it as a session-level variable. :-) SET synchronous_commit = 'on'; You could flip it on for the application-le

Re: Question: Is it possible to get the new xlog position after query execution?

> On Nov 8, 2021, at 10:03, Oleg Serov wrote: > That does not seem to be feasible for our application. Using synchronous > commit affects performance and really makes replication not really useful... > What we want to achieve is to have a consistent DB state across all > connections for mast

Re: libpq: How to cancel a COPY ... TO statement?

Daniel Frey writes: > after sending a COPY ... TO statement with PQsendQuery(), how can I cancel it > properly? > I tried using PQcancel(), That's the correct way. > but it seems to have no effect. Calling PQgetCopyData() or PQgetResult() > afterwards does not go into a failure state. And I d

libpq: How to cancel a COPY ... TO statement?

Hi, after sending a COPY ... TO statement with PQsendQuery(), how can I cancel it properly? I tried using PQcancel(), but it seems to have no effect. Calling PQgetCopyData() or PQgetResult() afterwards does not go into a failure state. And I don't want to call PQgetCopyData() until it returns

Re: Question: Is it possible to get the new xlog position after query execution?

> On Nov 7, 2021, at 19:42, Oleg Serov wrote: > How would you accomplish this otherwise? Synchronous commit. It sounds like you are attempting to build the same kind of guarantees that synchronous commit provides, only in the application by polling LSNs. It might be best just to use synchr

Re: Design database schemas around a common subset of objects

On 11/7/21 16:14, Erik Wienhold wrote: Hi Adrian, On 07/11/2021 18:38 Adrian Klaver wrote: My questions for this are: I'm thinking about something like merges in Git. Database schemas for project-a and project-b are like separate repositories and changes in core are merged as necessary.

Re: Mongo FDW For Postgres

On Mon, 2021-11-08 at 17:11 +0530, Dhivya E wrote: > Can i get proper documentation for Mongodb FDW extension installation For > Postgres ? Will it support AWS RDS and Aurora? Please advise. The Wiki lists three foreign data wrappers for MongoDB: https://wiki.postgresql.org/wiki/Foreign_data_wrap

Re: Mongo FDW For Postgres

Hi Team, Can i get proper documentation for Mongodb FDW extension installation For Postgres ? Will it support AWS RDS and Aurora? Please advise. -- Regards, Dhivya E Data Engineer Heptagon Technologies Pvt Ltd Website: https://heptagon.in Email: dhivy...@heptagon