| From: | Wasim Devale <wasimd60(at)gmail(dot)com> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org>, pgsql-admin <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: Restoration query |
| Date: | 2024-07-28 04:04:52 |
| Message-ID: | CAB5fag6hA4SY6HwJU0QchX7XKZz+EjGVYGRp2nD3+NjOt5xGrA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
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(dot)g(dot)johnston(at)gmail(dot)com> wrote:
> On Saturday, July 27, 2024, Wasim Devale <wasimd60(at)gmail(dot)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.
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2024-07-28 04:09:17 | Re: Restoration query |
| Previous Message | Ron Johnson | 2024-07-27 20:24:45 | Re: Faster pg_resore with autovacuum off? |