pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Holger Jakobs <holger@jakobs.com>
To: pgsql-admin@lists.postgresql.org
Subject: Re: Vacuum Full not clean the table
Date: Tue, 7 Feb 2023 19:47:02 +0100
Message-ID: <7927f0f1-517b-c3e3-a46a-edae56dee442@jakobs.com> (raw)
In-Reply-To: <CA+dvXXu1OMaJviuJ3vZhq-3Qe2EFEfRsQkTrdA+HviU-A1LV8w@mail.gmail.com>
References: <CA+dvXXu2krLsS3K_GJkdrCT1hbu+G0rxAjh1KKot5TGrBpn8AA@mail.gmail.com>
	<8aacabc6-5919-5f37-9c9a-2a3cd67adfa3@jakobs.com>
	<CA+dvXXu1OMaJviuJ3vZhq-3Qe2EFEfRsQkTrdA+HviU-A1LV8w@mail.gmail.com>

Am 07.02.23 um 19:45 schrieb Erik Serrano:
> Thank you very much Holger  for answering, I'll tell you... regarding 
> your question about whether it has enough provisioned space to be able 
> to do the vacuum, yes... yes it does.
> Regarding your indication of the version we are working on, I know 
> that 9.2 is out of all support and that its update is imminent... But 
> that's how it is right now and I have to deal with it...
>
> For this reason, I appreciate that you can even guide me to see what 
> is happening or could have happened regarding the end of the process 
> without the expected result, which is cleaning the table.
>
> Thank you in advance for your help
>
> /*
> */
> /*Erik R. Serrano Saavedra*/
> /*Ingeniero de Sistemas Informáticos*/
> /*      Data Base Administrator*/
> /*eserranos@gmail.com
> */
> /*                 998596691*/
> /**/
>
>
> El mar, 7 feb 2023 a las 13:56, Holger Jakobs (<holger@jakobs.com>) 
> escribió:
>
>     Am 07.02.23 um 17:51 schrieb Erik Serrano:
>>     Dear All,
>>
>>     Along with saying hello, I would like to consult about a failure
>>     that is happening to me with a PG 9.2 base and with a table that
>>     weighs 116GB and its index 13Gb, mounted on a Linux Centos 7.2
>>     with 4Core and 32Ram.
>>     The failure occurs mainly in that I execute a Vacuum Full on the
>>     table and it ends after 6 hours, but it does not clean anything.
>>     When checking the dead tuples I realize that they follow the same
>>     dirty records in the table. REF: (table of 420MM records with
>>     20MM dead tuples)
>>
>>     I hope you can guide me in finding a solution to clean that table.
>>
>>     Greetings and many thanks to the Postgresql.org community
>>     Atte.
>>
>>     /*
>>     */
>>     /*Erik Serrano*/
>>
>
>     Hi Erik,
>
>     Does it end cleanly or with an error after 6 hours?
>
>     Do you have enough disk space for the vacuum full? The old and the
>     newly written data have to exist at the same time. Only after a
>     successful vacuuming the old data get deleted.
>
>     BTW, PG 9.2 has been out of service for quite some time. Only
>     versions 11 to 15 are supported, with the support for version 11
>     lasting less than a year.
>
>     Kind Regards,
>
>     Holger
>
>     -- 
>     Holger Jakobs, Bergisch Gladbach, Tel. +49-178-9759012
>
Scott Ribe is right, the percentage of dead tuples is not high. So there 
no real reason to change anything.


-- 
Holger Jakobs, Bergisch Gladbach, Tel. +49-178-9759012



Attachments:

  [application/pgp-signature] OpenPGP_signature (202B, ../7927f0f1-517b-c3e3-a46a-edae56dee442@jakobs.com/3-OpenPGP_signature)
  download

view thread (8+ messages)  latest in thread

Message-ID: <7927f0f1-517b-c3e3-a46a-edae56dee442@jakobs.com>
Permalink:  ../7927f0f1-517b-c3e3-a46a-edae56dee442@jakobs.com/
Also on:    postgresql.org/message-id/7927f0f1-517b-c3e3-a46a-edae56dee442@jakobs.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: holger@jakobs.com, pgsql-admin@lists.postgresql.org
  Subject: Re: Vacuum Full not clean the table
  In-Reply-To: <7927f0f1-517b-c3e3-a46a-edae56dee442@jakobs.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox