Обсуждение: PostgresQL 12 - could not connect to server: FATAL: the database system is in recovery mode

Поиск
Список
Период
Сортировка

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

От
FOUTE K. Jaurès
Дата:
Hello,

How can i solve this error ?

--
Jaurès FOUTE 

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

От
Srinivasa T N
Дата:


On Mon, Jul 13, 2020, 7:16 PM FOUTE K. Jaurès <jauresfoute@gmail.com> wrote:
Hello,

How can i solve this error 

More info required

Regards,
Seenu.

--
Jaurès FOUTE 

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

От
FOUTE K. Jaurès
Дата:
Hello,

The problem is related to my previous email "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" .
After stopping the replication postgresql has restarted to respond.

Le lun. 13 juil. 2020 à 14:58, Srinivasa T N <seenutn@gmail.com> a écrit :


On Mon, Jul 13, 2020, 7:16 PM FOUTE K. Jaurès <jauresfoute@gmail.com> wrote:
Hello,

How can i solve this error 

More info required

Regards,
Seenu.

--
Jaurès FOUTE 


--
Jaurès FOUTE 
Technology Consultant
ISNOV SARL - Business Technology Consulting
Tel: +237 79395671 / +237 96248793
Email: jauresfoute@gmail.com
          jauresmelkiore@yahoo.fr
Compte Skype: jauresmelkiore

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

От
Adrian Klaver
Дата:
On 7/13/20 1:14 PM, FOUTE K. Jaurès wrote:
> Hello,
> 
> The problem is related to my previous email "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" .
> After stopping the replication postgresql has restarted to respond.

So you fixed the 'no space' issue?

The error message indicates that the server is running through the 
recovery process. Have you looked at the Postgres log to see where it is 
at in that or if is proceeding at all?

> 
> Le lun. 13 juil. 2020 à 14:58, Srinivasa T N <seenutn@gmail.com 
> <mailto:seenutn@gmail.com>> a écrit :
> 
> 
> 
>     On Mon, Jul 13, 2020, 7:16 PM FOUTE K. Jaurès <jauresfoute@gmail.com
>     <mailto:jauresfoute@gmail.com>> wrote:
> 
>         Hello,
> 
>         How can i solve this error
> 
> 
>     More info required
> 
>     Regards,
>     Seenu.
> 
> 
>         -- 
>         Jaurès FOUTE
> 
> 
> 
> -- 
> Jaurès FOUTE
> Technology Consultant
> ISNOV SARL - Business Technology Consulting
> Tel: +237 79395671 / +237 96248793
> Email: _jauresfoute@gmail.com <mailto:jauresfoute@gmail.com>_,
> jauresmelkiore@yahoo.fr <mailto:jauresmelkiore@yahoo.fr>
> Compte Skype: jauresmelkiore


-- 
Adrian Klaver
adrian.klaver@aklaver.com