Rural Hunter ruralhun...@gmail.com wrote:
This was changed quite long time ago when I saw too frequent auto
vacuums to prevent the wrap-around on a very busy/large table
which slow down the performance. I will change it back to the
default to see how it works.
There was a long-standing bug
于 2013/9/17 0:02, Kevin Grittner 写道:
Possibly. As I said before, I think the symptoms might better fit a
situation where the table in need of VACUUM was a shared table and it
just happened to mention db1 because that was the database it was
scanning at the time. (Every database includes the
Rural Hunter ruralhun...@gmail.com wrote:
I'm on Ubuntu 12.04.1 64bit with 32 cores and 377G memory. The
data is stored on several rai10 SAS 15k disks.
With a machine that beefy I have found it necessary to make the
autovacuum settings more aggressive. Otherwise the need for
vacuuming can
于 2013/9/16 1:31, Kevin Grittner 写道:
There's your problem. You left so little space between when
autovacuum would kick in for wraparound prevention (2 billion
transactions) and when the server prevents new transactions in
order to protect your data (2 ^ 31 - 100 transactions) that
Rural Hunter ruralhun...@gmail.com wrote:
Let me put here the whole scenario:
1. I was called by our application users that all the updating was
failing. So I went to check the db. Any update transaction including
manual vacuum is blocked out by the error message:
ERROR: database is not
于 2013/9/15 1:06, Kevin Grittner 写道:
Rural Hunter ruralhun...@gmail.com wrote:
Why in the world would you want to use VACUUM FULL in this circumstance?
the db name in the error message wrong?
I just googled around and found the solution. What's the other option?
There are two possibilities --
On Sat, Sep 14, 2013 at 6:05 PM, Rural Hunter ruralhun...@gmail.com wrote:
于 2013/9/15 1:06, Kevin Grittner 写道:
Rural Hunter ruralhun...@gmail.com wrote:
Why in the world would you want to use VACUUM FULL in this circumstance?
the db name in the error message wrong?
I just googled around
Rural Hunter escribió:
2. Since db1 is a very large database(it is the main db the user is
using) I can not afford to take long time to vacuum full on that. So
I thought about to try on other small dbs first.
3. I stop the instance.
4. I use echo 'vacuum full;' | postgres --single -D
