Postgres Pro
Downloads
Home   >   mailing lists

Re: Restoration query - Mailing list pgsql-admin

From Wasim Devale
Subject Re: Restoration query
Date
Msg-id CAB5fag6hA4SY6HwJU0QchX7XKZz+EjGVYGRp2nD3+NjOt5xGrA@mail.gmail.com
Whole thread Raw
In response to Re: Restoration query  ("David G. Johnston" <david.g.johnston@gmail.com>)
Responses Re: Restoration query
List pgsql-admin
Tree view

It's a .dmp custom format dump from Azure pipeline and it is of 250GB only.

I ran reindexing and vacuum but not full vacuum. So there cannot be an index or table bloating.

On Sun, 28 Jul, 2024, 12:05 am David G. Johnston, <david.g.johnston@gmail.com> wrote:
On Saturday, July 27, 2024, Wasim Devale <wasimd60@gmail.com> wrote:

After restoring data it shows 
data is 250 GB whereas production database has 352GB of data from where we took the backup.

Why this discrepancy? I have not run full vaccum on production database but it has been cleaned by vaccum and reindexing.


 Table and index bloat isn’t saved in a logical backup.

David J.

pgsql-admin by date:

Previous
From: Ron Johnson
Date:
Subject: Re: Faster pg_resore with autovacuum off?
Next
From: "David G. Johnston"
Date:
Subject: Re: Restoration query