From: | srinivasan s <srinioracledba7(at)gmail(dot)com> |
---|---|
To: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
Cc: | pgsql-admin(at)lists(dot)postgresql(dot)org |
Subject: | Re: Table size is constantly growing and causing performance problems |
Date: | 2025-02-12 07:35:58 |
Message-ID: | CAOEeMcWKhJRXjcCr9CPzVSjiZhGQVAiQ9gk-Dm8P8S5+Jxs3mQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Thanks @Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> , let me take a look at the
bug and view that you shared.
I didn't mention Vacuum full in my message, I mentioned vacuum analyze; it
is scheduled to run every weekend.
On Wed, Feb 12, 2025 at 1:00 PM Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
wrote:
> On Wed, 2025-02-12 at 10:14 +0530, srinivasan s wrote:
> > One of the tables in our database suddenly started growing very fast
> without
> > any changes to the environment. it has grown over 10GB in the last week
> and
> > this is causing performance issues. We ended up adding an index to solve
> the
> > performance problem but the table growth didn't stop. It is growing
> continuously.
> > we are using postgres version 12 on ubuntu
>
> That's a mistake. Use a supported version. As it is, you could be
> suffering
> from some already fixed (data corruption?) bug.
>
> > We are running a vacuum analsye on a full database every weekend and an
> auto
> > vacuum is set up.
>
> VACUUM (FULL) is also a mistake. It should be a regular VACUUM.
>
> Funny, you say that you are experiencing bloat. How can that be if you are
> running VACUUM (FULL)? Perhaps something is blocking VACUUM from removing
> dead rows:
>
> https://www.cybertec-postgresql.com/en/reasons-why-vacuum-wont-remove-dead-rows/
>
> > My observation on the DB so far.
> >
> > [...]
> >
> > 3. Also noticed that there is a auto vacuum job running on the table with
> > (to prevent wraparound)
> >
> > I am not sure if this auto vacuum (to prevent wraparound) is progressing,
> > it is running for more than 15 hours and status is active.
>
> You should check "pg_stat_progress_vacuum" to see if the numbers are
> changing,
> that is, if there is actually any progress. That may also give you a clue
> as
> to how long it will still take.
>
> Yours,
> Laurenz Albe
>
>
> --
>
> *E-Mail Disclaimer*
> Der Inhalt dieser E-Mail ist ausschliesslich fuer den
> bezeichneten Adressaten bestimmt. Wenn Sie nicht der vorgesehene Adressat
> dieser E-Mail oder dessen Vertreter sein sollten, so beachten Sie bitte,
> dass jede Form der Kenntnisnahme, Veroeffentlichung, Vervielfaeltigung
> oder
> Weitergabe des Inhalts dieser E-Mail unzulaessig ist. Wir bitten Sie, sich
> in diesem Fall mit dem Absender der E-Mail in Verbindung zu setzen.
>
> *CONFIDENTIALITY NOTICE & DISCLAIMER
> *This message and any attachment are
> confidential and may be privileged or otherwise protected from disclosure
> and solely for the use of the person(s) or entity to whom it is intended.
> If you have received this message in error and are not the intended
> recipient, please notify the sender immediately and delete this message
> and
> any attachment from your system. If you are not the intended recipient, be
> advised that any use of this message is prohibited and may be unlawful,
> and
> you must not copy this message or attachment or disclose the contents to
> any other person.
>
From | Date | Subject | |
---|---|---|---|
Next Message | Laurenz Albe | 2025-02-12 07:36:01 | Re: Security definer function to alter a sequence |
Previous Message | Laurenz Albe | 2025-02-12 07:29:59 | Re: Table size is constantly growing and causing performance problems |