| From: | Tommy Li <tommy(at)coffeemeetsbagel(dot)com> |
|---|---|
| To: | Stephen Frost <sfrost(at)snowman(dot)net> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: a verbose option for autovacuum |
| Date: | 2021-01-25 17:46:28 |
| Message-ID: | CAMifU2WKdAJn-vDUQ6eS8DvCEqjAP2GjgJ_jGRu4bF367T7xAQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi Stephen
> ... can set vacuum options on a table level which autovacuum should
respect,
> such as vacuum_index_cleanup and vacuum_truncate. For skip locked,
> autovacuum already will automatically release it's attempt to acquire a
> lock if someone backs up behind it for too long.
This is good information, I wasn't aware that autovacuum respected those
settings.
In that case I'd like to focus specifically on the verbose aspect.
My first thought was a new boolean configuration called
"autovacuum_verbose".
I'd want it to behave similarly to autovacuum_vacuum_cost_limit in that it
can be
set globally or on a per-table basis.
Thoughts?
Tommy
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2021-01-25 18:02:20 | Re: [Proposal] Global temporary tables |
| Previous Message | Robert Haas | 2021-01-25 17:38:27 | Re: CheckpointLock needed in CreateCheckPoint()? |