Dear Team,
We have upgraded PostgreSQL DB from version 13 to 15 version .
We are facing issue in PG15 we not enable any parameter related to AUTOVACUUM ,
but still running on PG15 data base.
Below process showing :
2313192 | 02:10:01.283176 || myLava | active | autovacuum:
Hi Team,
I am facing error during restore of PG_BASEBACKUP , server is not going UP
after restoring .
We follow below process .
1. First we take backup by command : pg_basebackup -h127.0.01 -U postgres -D
/mnt/backup
2. Maintain restore_command = 'cp /var/lib/pgsql/13/data/pg_log_archiv
Dear Adrian,
We are using "pg_log_archive" for Point-in-Time Recovery and DR replication.
Regards,
Ram Pratap.
-Original Message-
From: Adrian Klaver [mailto:adrian.kla...@aklaver.com]
Sent: 21 April 2022 21:35
To: Ram Pratap Maurya ;
pgsql-gene...@postgresql.org
Subject
Dear Adrian,
We are using binary replication and par day pg_log_archive total size is
increase after upgrade for PG11 to PG13.
Regards,
Ram Pratap.
-Original Message-
From: Adrian Klaver [mailto:adrian.kla...@aklaver.com]
Sent: 19 April 2022 22:51
To: Ram Pratap Maurya
icate from pg_log_archive.
Can you please suggest what changes need to required in PG13 conf file.
Regards,
Ram Pratap.
-Original Message-
From: Adrian Klaver [mailto:adrian.kla...@aklaver.com]
Sent: 18 April 2022 21:30
To: Ram Pratap Maurya
mailto:ram.mau...@lavaintern
Klaver [mailto:adrian.kla...@aklaver.com]
Sent: 18 April 2022 21:30
To: Ram Pratap Maurya ;
pgsql-gene...@postgresql.org
Cc: Manu Saxena
Subject: Re: Huge archive log generate in Postgresql-13
On 4/18/22 04:34, Ram Pratap Maurya wrote:
> Hi Support,
>
> We have upgraded postgresq
Hi Support,
We have upgraded postgresql DB from version 11 to 13 . after upgrade to 13
huge archive log generate in system .
Before upgrade per day 120GB to 150 GB log generated but after upgrade per day
approx. 250 to 300 GB log generated.
Can you please suggest why huge archive log generate
Hi Team,
Confirm what is Avg/max size of these JSON docs in Postgres.
Regards,
Ram Pratap.
: Ram Pratap Maurya; pgsql-general@lists.postgresql.org
Subject: Re: BUG #17046: Upgrade postgres 11 to 13 version
On 6/3/21 5:53 AM, Ram Pratap Maurya wrote:
> Hi Team,
>
> I am creating new server and installed postgres -13 and take PG_BACKUP form
> current PRD server (PG ver
Rowley [mailto:dgrowle...@gmail.com]
Sent: 03 June 2021 18:01
To: Ram Pratap Maurya; PostgreSQL mailing lists
Subject: Re: BUG #17046: Upgrade postgres 11 to 13 version
On Fri, 4 Jun 2021 at 00:22, PG Bug reporting form
wrote:
> i am creating new server and installed postgres -13 and take PG_BAC
Hello team,
I am facing the below error related to pg_basebackup.Tried to find solution.
I also see the DB log but we not found any backup failed error log.
[cid:image001.png@01D62D00.27C23FE0]
Regards,
Ram Pratap.
Lava International Limited.
Tel+ 91-120-4637148
[cid:image001.jpg@01CFD804.C42
20-4637148
[cid:image001.jpg@01CFD804.C427DF90]
From: Ravi Krishna [mailto:srkrish...@comcast.net]
Sent: 06 May 2020 16:28
To: Ram Pratap Maurya
Cc: pgsql-gene...@postgresql.org; Ashish Chugh
Subject: Re: Abnormal Growth of Index Size - Index Size 3x large than table
size.
On May 6, 2020, at 5:48 AM,
Hi Team,
We are facing a problem in our PostgreSQL production database related to
abnormal growth of index size. Some of the indexes are having abnormal growth
and index size is larger than table data size.
One table is having 75 G.B of index though table size is only 25 G.B. On
monthly basis w
13 matches
Mail list logo
