| From: | Luca Ferrari <fluca1978(at)gmail(dot)com> |
|---|---|
| To: | Sonam Sharma <sonams1209(at)gmail(dot)com> |
| Cc: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Change in db size |
| Date: | 2019-07-18 06:28:42 |
| Message-ID: | CAKoxK+52UjcWd67OH2gLZwr6vKqRTDz6Rg+6+2SadwHWa3wc1g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, Jul 17, 2019 at 7:33 PM Sonam Sharma <sonams1209(at)gmail(dot)com> wrote:
>
> I took the backup using pg_dump with gzip option and restored it with psql.
It does not change the way you backed up, chances are when you
restored it the database cropped table and index bloating as already
mentioned.
The other, remote chance, is that you did not backed up all the
objects, so in this case you should show us your backup command line
(and restore one too), and also the output of commands like \l+, \dt+,
\di+ and differences you have found.
Luca
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Cumer Cristiano | 2019-07-18 08:34:24 | Postgers 9.3 - ubuntu 16.04 - Are clogs entires automatically deleted? |
| Previous Message | Michael Harris | 2019-07-18 02:04:22 | pg_stat_progress_vacuum comes up empty ...? |