|From:||Tatsuo Ishii <ishii(at)postgresql(dot)org>|
|Cc:||alvherre(at)2ndquadrant(dot)com, robertmhaas(at)gmail(dot)com, ishii(at)postgresql(dot)org, tv(at)fuzzy(dot)cz, pgsql-hackers(at)postgresql(dot)org|
|Subject:||Re: pgbench -f and vacuum|
|Views:||Raw Message | Whole Thread | Download mbox | Resend email|
>>> Although that might be taking this thread rather far off-topic.
>> Not really sure about that, because the only outstanding objection to
>> this discussion is what happens in the startup stage if you specify -f.
>> Right now vacuum is attempted on the standard tables, which is probably
>> not the right thing in the vast majority of cases. But if we turn that
>> off, how do we reinstate it for the rare cases that want it? Personally
>> I would just leave it turned off and be done with it, but if we want to
>> provide some way to re-enable it, this --startup-script=FILE gadget
>> sounds like a pretty decent idea.
> (Catching up with this thread)
> Yes I think that it would be more simple to simply turn off the
> internal VACUUM if -f is specified. For the cases where we still need
> to vacuum the tables pgbench_*, we could simply document to run a
> VACUUM on them.
Agreed. Here is the patch to implement the idea: -f just implies -n.
SRA OSS, Inc. Japan
|Next Message||Fujii Masao||2015-02-09 06:18:04||Re: [REVIEW] Re: Compression of full-page-writes|
|Previous Message||Tom Lane||2015-02-09 01:21:10||Re: RangeType internal use|