From: | pinker <pinker(at)onet(dot)eu> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: VACUUM FULL doesn't reduce table size |
Date: | 2015-03-11 15:52:23 |
Message-ID: | 1426089143446-5841434.post@n5.nabble.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
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.
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.
--
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.
From | Date | Subject | |
---|---|---|---|
Next Message | Devrim Gündüz | 2015-03-11 16:35:06 | Re: compatibilty postgres 9.2 RHEL 6.4 |
Previous Message | Joseph Kregloh | 2015-03-11 14:34:40 | Re: Basic Question on Point In Time Recovery |