Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1spXF5-002BxP-LR for pgsql-general@arkaria.postgresql.org; Sat, 14 Sep 2024 18:11:32 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1spXF5-001JxA-7h for pgsql-general@arkaria.postgresql.org; Sat, 14 Sep 2024 18:11:31 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1spXEH-001EBi-Pn for pgsql-general@lists.postgresql.org; Sat, 14 Sep 2024 18:10:41 +0000 Received: from mail-ed1-x535.google.com ([2a00:1450:4864:20::535]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1spXEE-001Bvs-9C for pgsql-general@postgresql.org; Sat, 14 Sep 2024 18:10:41 +0000 Received: by mail-ed1-x535.google.com with SMTP id 4fb4d7f45d1cf-5c24c92f699so3097642a12.2 for ; Sat, 14 Sep 2024 11:10:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1726337438; x=1726942238; darn=postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=QU+CkOlXubThKlU+p8eyrBc8mW31nQKgzLTxI1r/N1Y=; b=WwSkoaPgFNOfDKcCT1rpT8Zu6vizkqN+xVwLrrbpzoUCtmxsxY8xOKF53PBkmKOxxL 9Zy2jg7452FePMeIwz22BTtWf4pLUth5i/36h6ZGQVhswW9kAz+LtFC2oc9IzAt5JVG2 CDiDIxyjaZ8xm8HkxrUK+A60MHs6wxjKe/X9lXsPvAGwki40TWLb/b6W6mHRz5YS6lFF 8wDDNFT5Lq0fVK/QTj21/aTicEhHE5fmmU0rpGdKu0asoktT6Rbe7pAXehaHxrS7Xkv7 IoIWPGfDpJjlvsfhlcAQavkpxmS4r9Fn0iYEC654qnGjzJV/ag3tIbv3Vpao7CAoC13K HBAw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1726337438; x=1726942238; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=QU+CkOlXubThKlU+p8eyrBc8mW31nQKgzLTxI1r/N1Y=; b=sxdZ+wRVeFe/zmIg1Fht+1gBJVaeGHaeGfwPy3hKq4VjRTVUW/uX4Zb0abfo11+SY5 nmLYZ2S9hyYho/YVqNgYCoZ7orOfJGCdbIXe6vs2CD0xBBkRaHzIvoFyGzQsfeEIeSZ3 wt6IGN9nO6Bo3ftYyCbvZlTPkt1m7Ynq+JRsmdbge5CZIEylrxn/0V7T4qdJy66Akw1j 0P8r/hoWyxOT7VYrahd9Unkgf5DNrxr2RoxsmjYOreW1q0/2pc9FpoQ7zpKqEXWKgrik LcY0KHyokh6NqXtDwLm3laBHItyqUNovE33rcatGvUewxQ5Vm4dNJd9WF/mJYbu12eV9 TvAg== X-Gm-Message-State: AOJu0YwkPhLlXsb1KtAIIXUL+9w1YWR/eWRx3t251TJdKqirKUMhxTB4 gtr8882zMA8rm0KJ8tHTbfWTPmn8K7pMaD9uPgRm1btAB3DNhBJlrqzgz8W+ulXkKHWD17/fJqw rigpydoKz+eZfO22HEUBJVNqCcB8= X-Google-Smtp-Source: AGHT+IEhOCuiDofJ7ckrzjqFOoCZCFFk0vpMr0gXKj7diismsG/aj2klQi1dBJmfV6TLyFvx6Tg9iRqja53PELoNomM= X-Received: by 2002:a50:eac9:0:b0:5c0:aad3:c8fc with SMTP id 4fb4d7f45d1cf-5c413e57b3dmr6038338a12.30.1726337437713; Sat, 14 Sep 2024 11:10:37 -0700 (PDT) MIME-Version: 1.0 References: <65a64890-17b9-45ec-8ac4-afb61794806c@aklaver.com> In-Reply-To: <65a64890-17b9-45ec-8ac4-afb61794806c@aklaver.com> From: Vinay Oli Date: Sat, 14 Sep 2024 23:40:26 +0530 Message-ID: Subject: Re: Reg: Size difference To: Adrian Klaver Cc: pgsql-general@postgresql.org Content-Type: multipart/alternative; boundary="000000000000bccc9c0622184156" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000bccc9c0622184156 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi I've checked the database size by meta command \l+ and even I checked from file system level du -sh 49181 folder. 49181 is the db oid. Pgwal directory is same 40gb at primary and standby servers. All the directories are of same size, 49181 folder (oid) is only having different size. Thanks, Vinay kumar On Sat, Sep 14, 2024, 10:59=E2=80=AFPM Adrian Klaver wrote: > On 9/14/24 10:19, Vinay Oli wrote: > > Hi Team > > > > I have been using PostgreSQL for the past 6 years. PostgreSQL has > > significantly impacted my life, providing me with great opportunities > > for knowledge and self-development. > > > > I'm currently facing a strange issue with PostgreSQL 15.0. I have a > > primary-standby setup that is in sync, with a replication slot in place= . > > There are 18 databases, and one of the databases on the primary side is > > 104 GB, while the same database on the standby side is 216 GB. Both are > > in sync with zero delay. > > How are you measuring the size? > > If you are measuring on the files system what is the size of the base/ > and pg_wal/ sub-directories in the %PG_DATA directoty? > > > > > Could this be a bug? If so, has it been resolved in newer releases? If > > it is not a bug, how can this issue be fixed? Is there a solution or an= y > > supporting documentation available? > > > > WAL and log files are being rotated properly. The issue is with a > > database named services_mfs. On the primary cluster, the services_mfs > > database is 104GB, but on the standby cluster, it is 216GB, even though > > both cluster are in sync. The standby database is only used in case of = a > > crash, which is managed by a Patroni cluster with etcd. > > > > > > > > Thanks, > > > > Vinay Kumar > > > > > > > > -- > Adrian Klaver > adrian.klaver@aklaver.com > > --000000000000bccc9c0622184156 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi=C2=A0

=C2= =A0I've checked the database size by meta command \l+ and even I checke= d from file system level du -sh 49181 folder. 49181 is the db oid.

Pgwal directory is same 40gb= at primary and standby servers.=C2=A0

All the directories are of same size,=C2=A0 49181 folder (oi= d)=C2=A0 is only having different size.=C2=A0



Thanks,=C2=A0
Vinay kumar

On Sat, Sep 14, 20= 24, 10:59=E2=80=AFPM Adrian Klaver <adrian.klaver@aklaver.com> wrote:
On 9/14/24 10:19, Vinay Oli wrote:
> Hi Team
>
> I have been using PostgreSQL for the past 6 years. PostgreSQL has
> significantly impacted my life, providing me with great opportunities =
> for knowledge and self-development.
>
> I'm currently facing a strange issue with PostgreSQL 15.0. I have = a
> primary-standby setup that is in sync, with a replication slot in plac= e.
> There are 18 databases, and one of the databases on the primary side i= s
> 104 GB, while the same database on the standby side is 216 GB. Both ar= e
> in sync with zero delay.

How are you measuring the size?

If you are measuring on the files system what is the size of the base/
and pg_wal/ sub-directories in the %PG_DATA directoty?

>
> Could this be a bug? If so, has it been resolved in newer releases? If=
> it is not a bug, how can this issue be fixed? Is there a solution or a= ny
> supporting documentation available?
>
> WAL and log files are being rotated properly. The issue is with a
> database named services_mfs. On the primary cluster, the services_mfs =
> database is 104GB, but on the standby cluster, it is 216GB, even thoug= h
> both cluster are in sync. The standby database is only used in case of= a
> crash, which is managed by a Patroni cluster with etcd.
>
>
>
> Thanks,
>
> Vinay Kumar
>
>
>

--
Adrian Klaver
adrian.klaver@aklaver.com

--000000000000bccc9c0622184156--