--On Mittwoch, Februar 11, 2009 13:18:11 -0500 Robert Haas
robertmh...@gmail.com wrote:
In any case it's not difficult to write a script that loops over all
of your tables with ALTER TABLE. It's probably not as fast as a
single UPDATE statement, but I suspect you'd need to have an enormous
Joshua D. Drake wrote:
On Tue, 2009-02-10 at 10:15 +0900, Tatsuo Ishii wrote:
Hi,
Is there any way to stop autovacuum temporarily?(other than edit
postgresql.conf and reload it) Pgpool-II does not want autovacuum
running while doing onlie recovery.
It would be a significant hack but you
On Tue, Feb 10, 2009 at 8:53 AM, Alvaro Herrera
alvhe...@commandprompt.com wrote:
I'm not sure that this calls for a change in autovacuum itself; it seems
to be that whatwe really need is the ability to change postgresql.conf
settings from the SQL interface. This has been discussed at length
Peter Eisentraut wrote:
Joshua D. Drake wrote:
It would be a significant hack but you could update pg_autovacuum to set
all relations to false.
Which will no longer work in 8.4.
More generally, it was pointed out to me that users apparently do
updates of pg_autovacuum to change settings
On Wed, 2009-02-11 at 14:21 -0300, Alvaro Herrera wrote:
Peter Eisentraut wrote:
Joshua D. Drake wrote:
It would be a significant hack but you could update pg_autovacuum to set
all relations to false.
Which will no longer work in 8.4.
More generally, it was pointed out to me that
Alvaro Herrera alvhe...@commandprompt.com writes:
Peter Eisentraut wrote:
More generally, it was pointed out to me that users apparently do
updates of pg_autovacuum to change settings on a bunch of tables at
once. We might get some complaints if we remove that facility.
Hmm, argh.
On Wed, Feb 11, 2009 at 1:10 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Alvaro Herrera alvhe...@commandprompt.com writes:
Peter Eisentraut wrote:
More generally, it was pointed out to me that users apparently do
updates of pg_autovacuum to change settings on a bunch of tables at
once. We might
Alvaro Herrera alvhe...@commandprompt.com wrote:
I'm not sure that this calls for a change in autovacuum itself; it seems
to be that whatwe really need is the ability to change postgresql.conf
settings from the SQL interface.
Sure. 'SET GLOBAL autovacuum = off' is a TODO item.
I have
On Wednesday 11 February 2009 20:10:46 Tom Lane wrote:
AFAIR we pointed out from day one that pg_autovacuum was a temporary
API that we were not promising to keep around. Anybody who was coding
against it with the expectation that they'd not have to change that code
later was willfully
Tatsuo Ishii wrote:
Hi,
Is there any way to stop autovacuum temporarily?(other than edit
postgresql.conf and reload it)
Hmm, no, that's the only way.
I'm not sure that this calls for a change in autovacuum itself; it seems
to be that whatwe really need is the ability to change
On Tue, 2009-02-10 at 10:15 +0900, Tatsuo Ishii wrote:
Hi,
Is there any way to stop autovacuum temporarily?(other than edit
postgresql.conf and reload it) Pgpool-II does not want autovacuum
running while doing onlie recovery.
It would be a significant hack but you could update pg_autovacuum
Is there any way to stop autovacuum temporarily?(other than edit
postgresql.conf and reload it) Pgpool-II does not want autovacuum
running while doing onlie recovery.
It would be a significant hack but you could update pg_autovacuum to set
all relations to false.
Thanks. Maybe it will
12 matches
Mail list logo
