| From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
| Cc: | Nikolay Samokhvalov <samokhvalov(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Michael Paquier <michael(at)paquier(dot)xyz> |
| Subject: | Re: log_autovacuum in Postgres 14 -- ordering issue |
| Date: | 2021-08-27 18:57:19 |
| Message-ID: | CAH2-WznKkOd-L6nWgn+OcveYreRnOtJU8BAJn5rxU0wboueVgw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Aug 26, 2021 at 10:28 PM Peter Geoghegan <pg(at)bowt(dot)ie> wrote:
> I'll commit this in a day or two, backpatching to 14. Barring any objections.
Actually, we also need to make the corresponding lines for ANALYZE
follow the same convention -- those really should be consistent. As in
the attached revision.
I haven't tried to address the issue with "I/O timings:" that I just
brought to Stephen's attention. We can handle that question
separately.
--
Peter Geoghegan
| Attachment | Content-Type | Size |
|---|---|---|
| v2-0001-Reorder-log_autovacuum_min_duration-log-output.patch | application/octet-stream | 5.5 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2021-08-27 19:15:43 | Re: Queries that should be canceled will get stuck on secure_write function |
| Previous Message | Andres Freund | 2021-08-27 18:46:48 | Re: Estimating HugePages Requirements? |