On 09/22/2014 10:21 PM, Joel Avni wrote:
Its version 9.3.5, whats interesting the that the table grew in size after
the vacuum full, which I did to try to see why the auto vacuum wasn¹t
working.
Please do not top post, it makes it difficult to follow the thread.
However, after I stopped the
I noticed that tables on my master PostgreSQL server were growing, and running
vacuum full analyze on them actually made them even bigger.
At the same time, a slave PostgreSQL server had fallen behind in trying to
replicate, and was stuck in constantly looping over ‘started streaming WAL from
On 09/22/2014 01:42 PM, Joel Avni wrote:
I noticed that tables on my master PostgreSQL server were growing, and
running vacuum full analyze on them actually made them even bigger.
First what version of Postgres are you using?
Second VACUUM FULL is usually not recommended for the reason you
It 9.3.5 and I did the manual vacuum to try to see where the problem might
be.
On 9/22/14, 4:04 PM, Adrian Klaver adrian.kla...@aklaver.com wrote:
On 09/22/2014 01:42 PM, Joel Avni wrote:
I noticed that tables on my master PostgreSQL server were growing, and
running vacuum full analyze on them
Its version 9.3.5, whats interesting the that the table grew in size after
the vacuum full, which I did to try to see why the auto vacuum wasn¹t
working.
However, after I stopped the PostgreSQL slave instance, then vacuum full
did result in a much much smaller size, as expected. So it appears to
