Re: pg_upgrade --copy-file-range
| От | Tomas Vondra |
|---|---|
| Тема | Re: pg_upgrade --copy-file-range |
| Дата | |
| Msg-id | eb8b6d6c-25fe-41a8-ad96-c4aa23c3ebdc@enterprisedb.com обсуждение |
| Ответ на | Re: pg_upgrade --copy-file-range (Robert Haas <robertmhaas@gmail.com>) |
| Список | pgsql-hackers |
On 3/28/24 21:45, Robert Haas wrote: > On Tue, Mar 26, 2024 at 2:09 PM Tomas Vondra > <tomas.vondra@enterprisedb.com> wrote: >> The patch I shared a couple minutes ago should fix this, effectively >> restoring the original debug behavior. I liked the approach with calling >> strategy_implementation a bit more, I wonder if it'd be better to go >> back to that for the "accelerated" copy methods, somehow. > > Somehow I don't see this patch? > It's here: https://www.postgresql.org/message-id/90866c27-265a-4adb-89d0-18c8dd22bc19%40enterprisedb.com I did change the subject to reflect that it's no longer about pg_upgrade, maybe that breaks the threading for you somehow? regards -- Tomas Vondra EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
В списке pgsql-hackers по дате отправления: