From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | pinker <pinker(at)onet(dot)eu>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: VACUUM FULL doesn't reduce table size |
Date: | 2015-03-11 20:15:39 |
Message-ID: | 5500A26B.4010709@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 03/11/2015 08:52 AM, pinker wrote:
> Adrian Klaver-4 wrote
>> Also per Kevin Grittner and Tom Lane there
>> is a Nabble issue at work where the list here is not seeing all the
>> information. Example:
>
> It's because I edited some post. Then is visible only on nabble because
> edited version isn't sent back to the mailing list.
Per previous suggestions I would post to this(pgsql-general) list
directly. Hidden information is not to going to be well received here
and will impede an answer to your issue, just saying.
>
>
> Adrian Klaver-4 wrote
>> Also per Kevin Grittner we are looking at a moving target, so some sort
>> of information about current state would be helpful.
>
> I'm doing pg_dump from snapshot - on production that isn't possible. Today
> at night my colleague will run vacuum full verbose on this table in
> production environment, so we will see if this problem occurs only on
> snapshot or was replicated from production.
Alright.
>
>
>
> --
> View this message in context: http://postgresql.nabble.com/VACUUM-FULL-doesn-t-reduce-table-size-tp5840782p5841434.html
> Sent from the PostgreSQL - general mailing list archive at Nabble.com.
>
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Tim Uckun | 2015-03-11 20:43:04 | Re: Benchmarking partitioning triggers and rules |
Previous Message | Martin Caverly | 2015-03-11 18:04:30 | Re: FW: Installation |