| From: | Álvaro Herrera <alvherre(at)kurilemu(dot)de> |
|---|---|
| To: | "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: PostgreSQL 19 Beta 1 release announcement draft |
| Date: | 2026-06-01 18:32:02 |
| Message-ID: | ahmrij0eNogWDm5J@alvherre.pgsql |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi Jon,
Reads pretty well, I think. Just a small observation:
On 2026-May-28, Jonathan S. Katz wrote:
> This release brings improvements to vacuum and maintenance operations.
> Autovacuum can now use parallel workers, which can be configured with the new
> `autovacuum_max_parallel_workers` setting, and a new autovacuum scoring system
> helps prioritize tables to vacuum. PostgreSQL 19 further enhances vacuum, adding
> a new strategy that lets table scans mark pages as visible and reduce future
> vacuuming work. Additionally, this release adds the new `REPACK` and
> `REPACK CONCURRENTLY` commands, which allow rebuilding tables with less
> operational overhead.
There's no REPACK CONCURRENTLY command. We added the REPACK command,
and an option for it called CONCURRENTLY, which must be given in parens.
Not sure of good wording for this in the release announce, but I think
listing those as two separate commands is a bit odd.
--
Álvaro Herrera Breisgau, Deutschland — https://www.EnterpriseDB.com/
"Nunca se desea ardientemente lo que solo se desea por razón" (F. Alexandre)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Álvaro Herrera | 2026-06-01 18:32:36 | Re: pgsql: Advance restart_lsn more eagerly in LogicalConfirmReceivedLocati |
| Previous Message | Sami Imseih | 2026-06-01 18:31:00 | Re: Unify parallel worker handling for index builds and instrumentation |