Postgres Pro
Downloads
Home   >   mailing lists

Re: R: Vacuum full: alternatives? - Mailing list pgsql-general

From Scott Mead
Subject Re: R: Vacuum full: alternatives?
Date
Msg-id CAKq0gvLf7PW_YxDMK+sRfmPOk7mW_z-UpMomcpr1kTbZ7nmmRg@mail.gmail.com
Whole thread Raw
In response to Re: R: Vacuum full: alternatives?  (Andreas Kretschmer <andreas@a-kretschmer.de>)
Responses Re: R: Vacuum full: alternatives?  (Melvin Davidson <melvin6925@gmail.com>)
Re: R: Vacuum full: alternatives?  (Guillaume Lelarge <guillaume@lelarge.info>)
Re: R: Vacuum full: alternatives?  (John R Pierce <pierce@hogranch.com>)
List pgsql-general
Tree view


On Mon, Jun 20, 2016 at 6:13 AM, Andreas Kretschmer <andreas@a-kretschmer.de> wrote:


Am 20.06.2016 um 11:43 schrieb Job:
Hi Andreas,

I would suggest run only autovacuum, and with time you will see a not
more growing table. There is no need for vacuum full.
So new record, when will be pg_bulkloaded, will replace "marked-free" location?


 exactly, that's the task for vacuum


I believe that free space is only available to UPDATE, not INSERT.

 


Andreas


--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general



--
--
Scott Mead
Sr. Architect
OpenSCG

pgsql-general by date:

Previous
From: Jeff Janes
Date:
Subject: Re: R: Vacuum full: alternatives?
Next
From: Melvin Davidson
Date:
Subject: Re: R: Vacuum full: alternatives?