From: | Sunil Jadhav <sunilbjpatil(at)gmail(dot)com> |
---|---|
To: | Sabyasachi Mukherjee <mukherjee(dot)sabyasachi(at)outlook(dot)com> |
Cc: | pgsql-admin(at)lists(dot)postgresql(dot)org |
Subject: | Re: Observation with Postgres table size |
Date: | 2024-05-10 14:07:42 |
Message-ID: | CAEQOu1ExcsUpAy==jRUHYbiyQW6Hm67M9vWNUcmEYGkjnmFK+w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Hi Dear,
Please carefully read the vacuum full documents if you try this this will
impacts on current transaction due to exclusive lock if this is production
db then you required a download time for that .
Thanks
Sunil
On Fri, 10 May, 2024, 7:27 pm Sabyasachi Mukherjee, <
mukherjee(dot)sabyasachi(at)outlook(dot)com> wrote:
> Hello All,
>
> I am having an issue with the size of a Postgres DB table.
> The table have 17 columns. Out of them 5 jsonb columns. The table had
> 470000 rows when I checked from DBBeaver it showed the table size 34GB.
> After I deleted many rows from the table - it has currently 27038 rows. But
> the size of the table still shows 34GB.
> I was expecting the size of the DB table to be reduced.
> I event restarted the PG DB server service.
> I am using Postgres v16 .
> Can any body please advise, how to reduce the size of the table?
>
> Sabyasachi Mukherjee
>
From | Date | Subject | |
---|---|---|---|
Next Message | Chris Hoover | 2024-05-10 14:12:26 | Adding future partition causes deadlock??? |
Previous Message | Alessandro Dentella | 2024-05-10 14:02:50 | cloudNativePg bootstrap from dump |