Re: why there is not VACUUM FULL CONCURRENTLY?
От | Antonin Houska |
---|---|
Тема | Re: why there is not VACUUM FULL CONCURRENTLY? |
Дата | |
Msg-id | 6347.1708105409@antos обсуждение исходный текст |
Ответ на | Re: why there is not VACUUM FULL CONCURRENTLY? (Alvaro Herrera <alvherre@alvh.no-ip.org>) |
Ответы |
Re: why there is not VACUUM FULL CONCURRENTLY?
|
Список | pgsql-hackers |
Alvaro Herrera <alvherre@alvh.no-ip.org> wrote: > This is great to hear. > > On 2024-Jan-31, Antonin Houska wrote: > > > Is your plan to work on it soon or should I try to write a draft patch? (I > > assume this is for PG >= 18.) > > I don't have plans for it, so if you have resources, please go for it. ok, I'm thinking how can the feature be integrated into the core. BTW, I'm failing to understand why cluster_rel() has no argument of the BufferAccessStrategy type. According to buffer/README, the criterion for using specific strategy is that page "is unlikely to be needed again soon". Specifically for cluster_rel(), the page will *definitely* not be used again (unless the VACCUM FULL/CLUSTER command fails): BufferTag contains the relatin file number and the old relation file is eventually dropped. Am I missing anything? -- Antonin Houska Web: https://www.cybertec-postgresql.com
В списке pgsql-hackers по дате отправления: