| From: | Scott Mead <scottm(at)openscg(dot)com> |
|---|---|
| To: | Andreas Kretschmer <andreas(at)a-kretschmer(dot)de> |
| Cc: | Job <Job(at)colliniconsulting(dot)it>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: R: Vacuum full: alternatives? |
| Date: | 2016-06-20 15:03:49 |
| Message-ID: | CAKq0gvLf7PW_YxDMK+sRfmPOk7mW_z-UpMomcpr1kTbZ7nmmRg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Mon, Jun 20, 2016 at 6:13 AM, Andreas Kretschmer <andreas(at)a-kretschmer(dot)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(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
>
--
--
Scott Mead
Sr. Architect
*OpenSCG <http://openscg.com>*
http://openscg.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Melvin Davidson | 2016-06-20 15:06:27 | Re: R: Vacuum full: alternatives? |
| Previous Message | Jeff Janes | 2016-06-20 14:52:24 | Re: R: Vacuum full: alternatives? |