Re: Restoration query
| От | Wasim Devale |
|---|---|
| Тема | Re: Restoration query |
| Дата | |
| Msg-id | CAB5fag6hA4SY6HwJU0QchX7XKZz+EjGVYGRp2nD3+NjOt5xGrA@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Restoration query ("David G. Johnston" <david.g.johnston@gmail.com>) |
| Ответы |
Re: Restoration query
|
| Список | 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.g.johnston@gmail.com> wrote:
On Saturday, July 27, 2024, Wasim Devale <wasimd60@gmail.com> wrote:After restoring data it showsdata 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 по дате отправления: