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

System level call trace might help little bit using strace/truss utility. Regards, Virendra Kumar On Wednesday, July 1, 2020, 9:26:09 PM PDT, Rene de Gek wrote: Hi Adrian, Thank you for your reply. This was one of the things that Matthias has also  suggested to us, referring to

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

Hi Adrian, Thank you for your reply. This was one of the things that Matthias has also suggested to us, referring to https://sybase.public.easerver.powerbuilder.narkive.com/MsoAXSQJ/problem-connecting-to-database-from-easerver-component . We do set the server type to ODBC. The error 999 shows

If crashes during VACUUM, will it recover from a checkpoint that is before the forzen transaction ID of VACUUM?

Hello All, When VACUUM starts, it will calculate a frozen transaction ID and freeze all tuples older than it. Will this frozen TXID younger than the latest checkpoint? If this is the case, then when the system crashes after VACUUM has deleted some dead tuples and the system recovers from this

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

raf writes: > FOUTE K. Jaurès wrote: >> The result of df -i >> >> Sys. de fichiers Inœuds IUtil. ILibre IUti% Monté sur >> udev 3065149433 30647161% /dev >> tmpfs 3072780665 30721151% /run >> /dev/sdb259973632 356029 596176031% / >>

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: > 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

Re: Different results from identical matviews

Anders Steinlein writes: > We have a materialized view from which a customer reported some > confusing/invalid results, leading us to inspect the query and not finding > anything wrong. Running the query defining the matview manually, or > creating a new (identical) materialized view returns the

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 7/1/20 2:21 PM, FOUTE K. Jaurès wrote: Le mer. 1 juil. 2020 à 22:15, Adrian Klaver > a écrit : On 7/1/20 11:21 AM, FOUTE K. Jaurès wrote: > > >     Has the problem occurred again? > > Yes > 2020-07-01 19: 19: 21.868 WAT

Different results from identical matviews

Hi folks, We have a materialized view from which a customer reported some confusing/invalid results, leading us to inspect the query and not finding anything wrong. Running the query defining the matview manually, or creating a new (identical) materialized view returns the correct result.

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 à 22:15, Adrian Klaver a écrit : > On 7/1/20 11:21 AM, FOUTE K. Jaurès wrote: > > > > > > > Has the problem occurred again? > > > > Yes > > 2020-07-01 19: 19: 21.868 WAT [24204] ERROR: could not receive data from > > WAL stream: ERROR: could not rename file "pg_logical /

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 7/1/20 11:21 AM, FOUTE K. Jaurès wrote: Le mer. 1 juil. 2020 à 15:45, Adrian Klaver > a écrit : On 6/30/20 10:51 PM, FOUTE K. Jaurès wrote: > > > >       From /var/lib/postgresql/12/main/pg_logical what does du -sh  show?

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 7/1/20 11:21 AM, FOUTE K. Jaurès wrote: Has the problem occurred again? Yes 2020-07-01 19: 19: 21.868 WAT [24204] ERROR: could not receive data from WAL stream: ERROR: could not rename file "pg_logical / snapshots / 1E-8567EB0.snap.22195.tmp" to "pg_logical / snapshots /

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 à 17:11, Alvaro Herrera a écrit : > On 2020-Jun-30, 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 >

Re: Can't seem to mix an inner and outer join in a query and get it to work right.

The convention here is to bottom post or inline responses. On Wed, Jul 1, 2020 at 9:51 AM David Gauthier wrote: > Actually, I want the outer join first. If it finds something, then move > on to the inner join and filter out all those that don't join to a rec with > 'autosmoke'. But if the

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 à 15:45, Adrian Klaver a écrit : > On 6/30/20 10:51 PM, FOUTE K. Jaurès wrote: > > > > > > > > > From /var/lib/postgresql/12/main/pg_logical what does du -sh show? > > Please show results as text, you can copy from terminal screen. > > > >

Re: Can't seem to mix an inner and outer join in a query and get it to work right.

Thanks! Actually, I want the outer join first. If it finds something, then move on to the inner join and filter out all those that don't join to a rec with 'autosmoke'. But if the outer join does not connect to the workarea_env table, then just return what you have (the purpose of the outer

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 2020-Jun-30, 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 >

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 10:51 PM, FOUTE K. Jaurès wrote:  From /var/lib/postgresql/12/main/pg_logical what does du -sh  show? Please show results as text, you can copy from terminal screen. root@hybride:/var/lib/postgresql/12/main/pg_logical# du -sh 16K . Has the problem occurred again?

Re: BDR node status stays as C, not ready

On 7/1/20 8:14 AM, Emrah Tema wrote: > 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? BDR is

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

Item 3 from my previous message is resolved. For some reason there was a line in the odbc.ini "ConnSettings = prepareThreshold=0" I think this is one of the things we have tried and forgot to remove. After removing it, the application still reports "code: 999, sqlerrortext: An invalid handle was

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?