| From: | Christophe Courtois <christophe(dot)courtois(at)dalibo(dot)com> |
|---|---|
| To: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Pgbench : vacuum default behaviour history |
| Date: | 2020-07-06 16:41:37 |
| Message-ID: | 5d78a46f-d7a8-dd35-644b-367488fb60ce@dalibo.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hi,
We're wondering why pgbench behaves this way by default:
"With neither -n nor -v,
pgbench will vacuum the pgbench_tellers and pgbench_branches tables, and
will truncate pgbench_history."
Why pgbench_accounts not vacuumed by default?
I've dug the history of pgbench until 1999. The vaccum of
tellers|branches was added when creating the pgbench contrib in Jan
2000, but I've not found any explanation or discussion.
My hypothesis is that vaccuuming the accounts was too long in 1999, so
it could be skipped for quick tests. And it was never changed.
Did I miss something?
--
Christophe Courtois
Consultant Dalibo
https://dalibo.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sebastien Arod | 2020-07-06 16:43:31 | Is postgres able to share sorts required by common partition window functions? |
| Previous Message | legrand legrand | 2020-07-06 15:35:51 | Re: SV: Using Postgres jdbc driver with Oracle SQL Developer |