BDR node status stays as C, not ready

I am trying to make multimaster replication but when I use bdr_init_copy the database is copied from remote node but the status of the node stays as C, not R so Ready and for this reason the replication is not made. What should I do?

Re: PostgreSQL 12 - ERROR: could not rename file "pg_logical/snapshots/1A-7C00D890.snap.13594.tmp" to "pg_logical/snapshots/1A-7C00D890.snap": No space left on device

Le mer. 1 juil. 2020 à 00:11, raf a écrit : > FOUTE K. Jaurčs wrote: > > > Hi everyone, > > > > I am use a native logical replication in PostgreSQL 12 on Ubuntu 16.04 > and > > all is working fine until i faced this error below. > > > > ERROR: could not rename file > > "pg_logical/snapshots/1A-7

Re: PostgreSQL 12 - ERROR: could not rename file "pg_logical/snapshots/1A-7C00D890.snap.13594.tmp" to "pg_logical/snapshots/1A-7C00D890.snap": No space left on device

Le mar. 30 juin 2020 à 22:36, Adrian Klaver a écrit : > On 6/30/20 1:47 PM, FOUTE K. Jaurès wrote: > > > > > > Le mar. 30 juin 2020 à 21:23, Bruce Momjian > > a écrit : > > > > On Tue, Jun 30, 2020 at 01:16:58PM -0700, Adrian Klaver wrote: > > > On 6/30/20 11:03

Re: restart_lsn is not advancing

one more detail: pg_replication_slots.catalog_xmin shows the biggest age in the system. How could transaction on catalogues may affect logical slot. Any clue here ? Thank you, Rado On Wed, Jul 1, 2020 at 2:09 AM Radoslav Nedyalkov wrote: > Hello All, > we are in a situation where restart_lsn f

Re: PostgreSQL 12 - ERROR: could not rename file "pg_logical/snapshots/1A-7C00D890.snap.13594.tmp" to "pg_logical/snapshots/1A-7C00D890.snap": No space left on device

FOUTE K. Jaurès wrote: > Hi everyone, > > I am use a native logical replication in PostgreSQL 12 on Ubuntu 16.04 and > all is working fine until i faced this error below. > > ERROR: could not rename file > "pg_logical/snapshots/1A-7C00D890.snap.13594.tmp" to > "pg_logical/snapshots/1A-7C00D890.

restart_lsn is not advancing

Hello All, we are in a situation where restart_lsn for logical replication slots is not advancing. We have two slots. Both are active, confirmed_flush_lsn also is updated. Client side all looks okay. remote_lsn for subscritions is advancing. The effect of restart_lsn being 'stopped' is the disk i

Re: PostgreSQL 12 - ERROR: could not rename file "pg_logical/snapshots/1A-7C00D890.snap.13594.tmp" to "pg_logical/snapshots/1A-7C00D890.snap": No space left on device

On 6/30/20 1:47 PM, FOUTE K. Jaurès wrote: Le mar. 30 juin 2020 à 21:23, Bruce Momjian > a écrit : On Tue, Jun 30, 2020 at 01:16:58PM -0700, Adrian Klaver wrote: > On 6/30/20 11:03 AM, FOUTE K. Jaurès wrote: > > Hi everyone, > > > > I am use a

Re: PostgreSQL 12 - ERROR: could not rename file "pg_logical/snapshots/1A-7C00D890.snap.13594.tmp" to "pg_logical/snapshots/1A-7C00D890.snap": No space left on device

On Tue, Jun 30, 2020 at 10:03:52PM +0100, FOUTE K. Jaurès wrote: > Le mar. 30 juin 2020 à 21:23, Bruce Momjian a écrit : > > On Tue, Jun 30, 2020 at 01:16:58PM -0700, Adrian Klaver wrote: > > On 6/30/20 11:03 AM, FOUTE K. Jaurès wrote: > > > Hi everyone, > > > > > > I am use a

Re: PostgreSQL 12 - ERROR: could not rename file "pg_logical/snapshots/1A-7C00D890.snap.13594.tmp" to "pg_logical/snapshots/1A-7C00D890.snap": No space left on device

Le mar. 30 juin 2020 à 21:23, Bruce Momjian a écrit : > On Tue, Jun 30, 2020 at 01:16:58PM -0700, Adrian Klaver wrote: > > On 6/30/20 11:03 AM, FOUTE K. Jaurès wrote: > > > Hi everyone, > > > > > > I am use a native logical replication in PostgreSQL 12 on Ubuntu 16.04 > > > and all is working fin

Re: Connecting Powerbuilder / EAserver to PostgreSQL server 11 via ODBC or JDBC

> > So what operation is eroding out? > Can you try to isolate it? > > Thank you. Hi, Thank you for posting the question Matthias! And for your replies. We've now managed to collect the log files now from the application, driver manager and driver. And there are actually some things that might b

Re: PostgreSQL 12 - ERROR: could not rename file "pg_logical/snapshots/1A-7C00D890.snap.13594.tmp" to "pg_logical/snapshots/1A-7C00D890.snap": No space left on device

On Tue, Jun 30, 2020 at 01:16:58PM -0700, Adrian Klaver wrote: > On 6/30/20 11:03 AM, FOUTE K. Jaurès wrote: > > Hi everyone, > > > > I am use a native logical replication in PostgreSQL 12 on Ubuntu 16.04 > > and all is working fine until i faced this error below. > > From below it looks like you

Re: PostgreSQL 12 - ERROR: could not rename file "pg_logical/snapshots/1A-7C00D890.snap.13594.tmp" to "pg_logical/snapshots/1A-7C00D890.snap": No space left on device

On 6/30/20 11:03 AM, FOUTE K. Jaurès wrote: Hi everyone, I am use a native logical replication in PostgreSQL 12 on Ubuntu 16.04 and all is working fine until i faced this error below. From below it looks like you are using pg_logical which is a third party package. It is what the builtin log

Re: Logical Replication Issue

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

PostgreSQL 12 - ERROR: could not rename file "pg_logical/snapshots/1A-7C00D890.snap.13594.tmp" to "pg_logical/snapshots/1A-7C00D890.snap": No space left on device

Hi everyone, I am use a native logical replication in PostgreSQL 12 on Ubuntu 16.04 and all is working fine until i faced this error below. ERROR: could not rename file "pg_logical/snapshots/1A-7C00D890.snap.13594.tmp" to "pg_logical/snapshots/1A-7C00D890.snap": No space left on device Is there

Re: Logical Replication Issue

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?

Logical Replication Issue

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

Is there a way to execute queries in plpython without increasing txid after each query?

I noticed that each query in plpython3 is executed in its own subtransaction ( https://github.com/postgres/postgres/blob/257ee34e733aba0fc371177f1a7fd97f3cb98d74/src/pl/plpython/plpy_spi.c#L226) which increases txid. For example: CREATE EXTENSION IF NOT EXISTS plpython3u; DROP TABLE IF EXISTS de