Re: PostgreSQL 13 - Logical Replication - ERROR: could not receive data from WAL stream: SSL SYSCALL error: EOF detected

2023-05-19 Thread FOUTE K . Jaurès
Le ven. 19 mai 2023 à 05:02, Kyotaro Horiguchi a écrit : > At Thu, 18 May 2023 21:00:08 +0100, FOUTE K. Jaurès > wrote in > > Hello everyone, > > > > I have a replication between PostgreSQL 12 to 13 in the production > system. > > Using Ubuntu 18.04

PostgreSQL 13 - Logical Replication - ERROR: could not receive data from WAL stream: SSL SYSCALL error: EOF detected

2023-05-18 Thread FOUTE K . Jaurès
Hello everyone, I have a replication between PostgreSQL 12 to 13 in the production system. Using Ubuntu 18.04 LTS We have this error today. *2023-05-18 18:34:04.374 WAT [117322] ERROR: could not receive data from WAL stream: SSL SYSCALL error: EOF detected2023-05-18 18:34:04.381 WAT [118393] L

Re: PG_Cron - Error Message Connection failed

2023-05-15 Thread FOUTE K . Jaurès
Le lun. 15 mai 2023 à 05:12, FOUTE K. Jaurès a écrit : > > > Le dim. 14 mai 2023 à 21:12, Adrian Klaver a > écrit : > >> On 5/14/23 13:04, FOUTE K. Jaurès wrote: >> > >> > >> > Le dim. 14 mai 2023 à 16:12, Adrian Klaver > > <mailto:adrian

Re: PG_Cron - Error Message Connection failed

2023-05-14 Thread FOUTE K . Jaurès
Le dim. 14 mai 2023 à 21:12, Adrian Klaver a écrit : > On 5/14/23 13:04, FOUTE K. Jaurès wrote: > > > > > > Le dim. 14 mai 2023 à 16:12, Adrian Klaver > <mailto:adrian.kla...@aklaver.com>> a écrit : > > > > > Not what was requested. > &g

Re: PG_Cron - Error Message Connection failed

2023-05-14 Thread FOUTE K . Jaurès
Le dim. 14 mai 2023 à 16:12, Adrian Klaver a écrit : > On 5/14/23 00:20, FOUTE K. Jaurès wrote: > > > > > > Le sam. 13 mai 2023 à 15:59, Adrian Klaver > <mailto:adrian.kla...@aklaver.com>> a écrit : > > > >

Re: PG_Cron - Error Message Connection failed

2023-05-14 Thread FOUTE K . Jaurès
Le sam. 13 mai 2023 à 15:59, Adrian Klaver a écrit : > On 5/13/23 00:54, FOUTE K. Jaurès wrote: > > > > > > > > > In your original post in the image under the database column it looks > > like, to my old eyes, there is a list of database

Re: PG_Cron - Error Message Connection failed

2023-05-13 Thread FOUTE K . Jaurès
Le ven. 12 mai 2023 à 20:21, Adrian Klaver a écrit : > On 5/12/23 09:41, FOUTE K. Jaurès wrote: > > Understand @Adrian Klaver <mailto:adrian.kla...@aklaver.com> . > > the log show: > > 2023-05-12 17:30:19.327 WAT [46190] LOG: cron job 8 starting: SELECT 1 > > 2

Re: PG_Cron - Error Message Connection failed

2023-05-12 Thread FOUTE K . Jaurès
Understand @Adrian Klaver . the log show: 2023-05-12 17:30:19.327 WAT [46190] LOG: cron job 8 starting: SELECT 1 2023-05-12 17:30:19.339 WAT [46190] LOG: cron job 8 connection failed Le ven. 12 mai 2023 à 17:23, Adrian Klaver a écrit : > On 5/12/23 09:22, FOUTE K. Jaurès wrote: > >

Re: PG_Cron - Error Message Connection failed

2023-05-12 Thread FOUTE K . Jaurès
quot;localhost", change it (via an UPDATE) to the address defined in > "listen_address" parameter and see if this works. > > > Em sex., 12 de mai. de 2023 às 17:00, FOUTE K. Jaurès < > jauresfo...@gmail.com> escreveu: > >> Hello everyone, >>

PG_Cron - Error Message Connection failed

2023-05-12 Thread FOUTE K . Jaurès
Hello everyone, Can someone help me to understand this issue. I installed and configured pg_cron on the server and I was able to connect without providing a password using psql command line. But when i schedule a job, like this: SELECT cron.schedule( 'TEST','30 seconds', $$SELECT 1$$); the result

Re: Materialized Views - Way to refresh automatically (Incrementaly)

2023-05-11 Thread FOUTE K . Jaurès
hello Thomas, Thanks, I'll check it out. Le jeu. 11 mai 2023 à 12:01, Thomas Boussekey a écrit : > Hello > > Le jeu. 11 mai 2023, 12:46, FOUTE K. Jaurès a > écrit : > >> Hello Everyone, >> >> Is There a way on PostgresQL 14 to automatically increment a

Materialized Views - Way to refresh automatically (Incrementaly)

2023-05-11 Thread FOUTE K . Jaurès
Hello Everyone, Is There a way on PostgresQL 14 to automatically increment a Materialized Views ? -- Jaurès FOUTE

Re: Call a Normal function inside a Trigger Function

2023-04-16 Thread FOUTE K . Jaurès
Thanks @Adrian Klaver It's clear for me now. On Sun, 16 Apr 2023, 20:13 Adrian Klaver, wrote: > On 4/16/23 11:47, FOUTE K. Jaurès wrote: > > Can I have an example please? Or a link > > create table trg_test (id integer, fld_1 varchar, fld_2 boolean); > > &g

Re: Call a Normal function inside a Trigger Function

2023-04-16 Thread FOUTE K . Jaurès
Can I have an example please? Or a link On Sun, 16 Apr 2023, 17:08 Pavel Stehule, wrote: > Hi > > > ne 16. 4. 2023 v 16:15 odesílatel FOUTE K. Jaurès > napsal: > >> Hello, >> >> Is it possible to call a function inside a trigger function ? >> Any i

Call a Normal function inside a Trigger Function

2023-04-16 Thread FOUTE K . Jaurès
Hello, Is it possible to call a function inside a trigger function ? Any idea or link are welcome. Thanks in advance Best Regards -- Jaurès FOUTE

Re: PostgreSQL - Ordering Table based of Foreign Key

2021-10-04 Thread FOUTE K . Jaurès
3 oct. 2021 à 22:33, David G. Johnston a écrit : > > > On Sun, Oct 3, 2021, 00:48 FOUTE K. Jaurès wrote: > >> Hello, >> >> I want to order tables based on the foreign key so that I can delete >> tables one by one without facing "ERROR: update or delete on t

Re: PostgreSQL - Ordering Table based of Foreign Key

2021-10-03 Thread FOUTE K . Jaurès
I need to delete data from about 100 table in the production system for a specific client without stopping application. On Sun, 3 Oct 2021, 17:19 Adrian Klaver, wrote: > On 10/3/21 7:40 AM, FOUTE K. Jaurès wrote: > > Thanks for your input but I want to make a delete with where clause

Re: PostgreSQL - Ordering Table based of Foreign Key

2021-10-03 Thread FOUTE K . Jaurès
Thanks for your input but I want to make a delete with where clause On Sun, 3 Oct 2021, 10:26 Andreas Joseph Krogh, wrote: > På søndag 03. oktober 2021 kl. 10:49:49, skrev Thomas Kellerer < > sham...@gmx.net>: > > FOUTE K. Jaurès schrieb am 03.10.2021 um 09:48: > > I wa

PostgreSQL - Ordering Table based of Foreign Key

2021-10-03 Thread FOUTE K . Jaurès
Hello, I want to order tables based on the foreign key so that I can delete tables one by one without facing "ERROR: update or delete on table "table" violates foreign key constraint. DETAIL: Key is still referenced from table" Any help is appreciated. Thank you in advance. Best regards Jaurès F

Re: PostgreSQL 12 - ERROR: invalid attribute number 2 for ad_user_pkey - Urgent

2021-09-01 Thread FOUTE K . Jaurès
After running: REINDEX TABLE pg_catalog.pg_attribute ; Le mer. 1 sept. 2021 à 17:54, FOUTE K. Jaurès a écrit : > Hello Tom, > > Thank You for your Answer. It solves the problem. > Thank you very much for your support. > > Le mer. 1 sept. 2021 à 16:46, Tom Lane a écrit : >

Re: PostgreSQL 12 - ERROR: invalid attribute number 2 for ad_user_pkey - Urgent

2021-09-01 Thread FOUTE K . Jaurès
Hello Tom, Thank You for your Answer. It solves the problem. Thank you very much for your support. Le mer. 1 sept. 2021 à 16:46, Tom Lane a écrit : > =?UTF-8?Q?FOUTE_K=2E_Jaur=C3=A8s?= writes: > > For all table except the pg_catalo table. > > The dump on the database is not possible too. (pg_d

Re: PostgreSQL 12 - ERROR: invalid attribute number 2 for ad_user_pkey - Urgent

2021-09-01 Thread FOUTE K . Jaurès
For all table except the pg_catalo table. The dump on the database is not possible too. (pg_dump: error: invalid column numbering in table "xx") Le mer. 1 sept. 2021 à 16:27, Adrian Klaver a écrit : > On 9/1/21 8:08 AM, FOUTE K. Jaurès wrote: > > Hello, > > > &

Re: PostgreSQL 12 - ERROR: invalid attribute number 2 for ad_user_pkey - Urgent

2021-09-01 Thread FOUTE K . Jaurès
I already restart the server (x3) Le mer. 1 sept. 2021 à 16:25, David G. Johnston a écrit : > On Wed, Sep 1, 2021 at 8:08 AM FOUTE K. Jaurès > wrote: > >> Any idea how to solve this issue is really appreciated >> > > Have you restarted the server? > &g

Re: PostgreSQL 12 - ERROR: invalid attribute number 2 for ad_user_pkey - Urgent

2021-09-01 Thread FOUTE K . Jaurès
No, I am using PostgreSQL 12 (Server and Client) Le mer. 1 sept. 2021 à 16:12, Rob Sargent a écrit : > > > On Sep 1, 2021, at 8:08 AM, FOUTE K. Jaurès wrote: > > Hello, > > I have a strange issue in a production database on a customer and need to > help to know

PostgreSQL 12 - ERROR: invalid attribute number 2 for ad_user_pkey - Urgent

2021-09-01 Thread FOUTE K . Jaurès
Hello, I have a strange issue in a production database on a customer and need to help to know how to solve the problem. Any select on the table other than pg_catalog table throws the error FATAL: catalog is missing 1 attribute(s) for Any idea how to solve this issue is really appreciated

Re: ERROR: could not start WAL streaming: ERROR: replication slot "XXX" does not exist

2021-03-28 Thread FOUTE K . Jaurès
Curiously the slot is not dropped. Le sam. 27 mars 2021 à 20:31, Atul Kumar a écrit : > As per your error, it seems replication slot has been dropped. > > On Saturday, March 27, 2021, FOUTE K. Jaurès > wrote: > >> Hello EveryOne, >> >> How can I solve Issue. ?

ERROR: could not start WAL streaming: ERROR: replication slot "XXX" does not exist

2021-03-27 Thread FOUTE K . Jaurès
Hello EveryOne, How can I solve Issue. ??? *ERROR: could not start WAL streaming: ERROR: replication slot "XXX" does not exist2021-03-27 11:48:33.012 WAT [1090] LOG: background worker "logical replication worker" (PID 8458) exited with exit code 12021-03-27 11:48:38.019 WAT [8461] LOG: logi

ERROR: terminating logical replication worker due to timeout

2020-10-02 Thread FOUTE K . Jaurès
Hello Everyone, How can I handle this error. Any idea ? I am usin PostgreSQL 12 on both Server. The error appear on the slave. My OS is Ubuntu Server 18.04 -- Jaurès FOUTE

Re: ERROR: canceling statement due to user request

2020-08-05 Thread FOUTE K . Jaurès
Le mer. 5 août 2020 à 11:57, Pavel Stehule a écrit : > > > st 5. 8. 2020 v 12:51 odesílatel FOUTE K. Jaurès > napsal: > >> Ok, >> Just want if we can avoid this error message, With some config for >> exemple ? >> > > it is not possible > Ok Th

Re: ERROR: canceling statement due to user request

2020-08-05 Thread FOUTE K . Jaurès
Ok, Just want if we can avoid this error message, With some config for exemple ? Le mer. 5 août 2020 à 11:07, Paul Förster a écrit : > Hi Jaurès, > > > On 05. Aug, 2020, at 11:35, FOUTE K. Jaurès > wrote: > > > > Hello, > > > > How can I Solve this erro

ERROR: canceling statement due to user request

2020-08-05 Thread FOUTE K . Jaurès
Hello, How can I Solve this error ? ERROR: canceling statement due to user request Best Regards, -- Jaurès FOUTE

Re: Questions about Logical Replication - Issue ???

2020-07-31 Thread FOUTE K . Jaurès
hello Kyotaro, thx for you feedback and clarification. Le ven. 31 juil. 2020 à 02:13, Kyotaro Horiguchi a écrit : > Hi, > > At Thu, 30 Jul 2020 14:54:08 +0100, FOUTE K. Jaurès > wrote in > > Hi everyone, > > > > Situation: > > > >- A Master Da

Questions about Logical Replication - Issue ???

2020-07-30 Thread FOUTE K . Jaurès
Hi everyone, Situation: - A Master Database on the HQ - i make a dump of the master database to the Subdivision Server - I create à Publication like: CREATE PUBLICATION iNOV_MasterData_Table_Pub FOR TABLE M_Product; On the Master Database - On the Subdivision Server, I create a Sub

PostgreSQL make too long to start.

2020-07-17 Thread FOUTE K . Jaurès
It is make sense that PostgreSQL make too long to start, About 20 minutes. I'm using PostgreSQL 12 intalling on Ubuntu Server 18.04 and my database is about 25 GO of data.

Re: PostgresQL 12 - could not connect to server: FATAL: the database system is in recovery mode

2020-07-13 Thread FOUTE K . Jaurès
tarted to respond. Le lun. 13 juil. 2020 à 14:58, Srinivasa T N a écrit : > > > On Mon, Jul 13, 2020, 7:16 PM FOUTE K. Jaurès > wrote: > >> Hello, >> >> How can i solve this error >> > > More info required > > Regards, > Seenu. > >

PostgresQL 12 - could not connect to server: FATAL: the database system is in recovery mode

2020-07-13 Thread FOUTE K . Jaurès
Hello, How can i solve this error ? -- Jaurès FOUTE

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

2020-07-08 Thread FOUTE K . Jaurès
Hello Raf, Tom, After many tests of proposal solutions, I am not able to solve the issue. Seems that It is a bug ? Le jeu. 2 juil. 2020 à 01:59, Tom Lane a écrit : > raf writes: > > FOUTE K. Jaurès wrote: > >> The result of df -i > >> > >> Sys. de fi

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

2020-07-01 Thread FOUTE K . Jaurès
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

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

2020-07-01 Thread FOUTE K . Jaurès
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: 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

2020-07-01 Thread FOUTE K . Jaurès
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 s

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

2020-06-30 Thread FOUTE K . Jaurès
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

2020-06-30 Thread FOUTE K . Jaurès
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 > <mailto:br...@momjian.us>> a écrit : > > > > On Tue, Jun 30, 2020 at 01:16:58PM -0700,

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

2020-06-30 Thread FOUTE K . Jaurès
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 U

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

2020-06-30 Thread FOUTE K . Jaurès
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