| 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 05:52:38 |
| Message-ID: | CAB5fag5QvYec+0Tmyq08FXc5q+jkt6mSHOKR8aAwFua_Q8W6kQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
I found some unusual it is not related to vaccum it is related to metadata
stored in a table.
That table has only 1 lakh rows but it shows 97 GB of size anything you
know about this?
On Sun, 28 Jul, 2024, 10:31 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:
>
>> So the live data is not getting restored? Did not get you. I have checked
>> the same data has been transferred to the tables rows match.
>>
>
> If you aren’t comparing vacuum full tables in the source database why do
> you expect the sizes to match?
>
> David J.
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Wasim Devale | 2024-07-28 07:39:04 | Stream pg_dumpall directly from CentOS7 to Red Hat server |
| Previous Message | David G. Johnston | 2024-07-28 05:01:52 | Re: Restoration query |