| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
| Cc: | Peter Geoghegan <pg(at)bowt(dot)ie>, postgresql(at)taljaren(dot)se, pgsql-hackers(at)lists(dot)postgresql(dot)org, Michael Paquier <michael(at)paquier(dot)xyz> |
| Subject: | Re: BUG #17717: Regression in vacuumdb (15 is slower than 10/11 and possible memory issue) |
| Date: | 2022-12-29 17:22:58 |
| Message-ID: | 576868.1672334578@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
I wrote:
> Justin Pryzby <pryzby(at)telsasoft(dot)com> writes:
>> I assumed it would look like:
>> VACUUM (UPDATE_DATABASE_STATS {yes,no,only})
> Meh. We could do it like that, but I think options that look like
> booleans but aren't are messy.
Note that I'm not necessarily objecting to there being just one option,
only to its values being a superset-of-boolean. Perhaps this'd work:
VACUUM (DATABASE_STATS {UPDATE,SKIP,ONLY})
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Bug reporting form | 2022-12-29 18:16:19 | BUG #17734: Doc bug: "initial database user" used where "bootstrap superuser" is meant |
| Previous Message | Tom Lane | 2022-12-29 15:14:32 | Re: postgres reorders expressions when inlining |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2022-12-29 17:23:30 | Re: postgres_fdw uninterruptible during connection establishment / ProcSignalBarrier |
| Previous Message | Andres Freund | 2022-12-29 17:21:01 | Re: Avoiding unnecessary clog lookups while freezing |