pg_upgrade --clone error checking

Поиск
Список
Период
Сортировка
От Jeff Janes
Тема pg_upgrade --clone error checking
Дата
Msg-id CAMkU=1yf4Z2xmD_Km0X3nAMH4_hfFDhC_kDtTBo0SOnjX-JgaQ@mail.gmail.com
обсуждение исходный текст
Ответы Re: pg_upgrade --clone error checking  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Список pgsql-hackers
With the new pg_upgrade --clone, if we are going to end up throwing the error "file cloning not supported on this platform" (which seems to depend only on ifdefs) I think we should throw it first thing, before any other checks are done and certainly before pg_dump gets run.

This might result in some small amount of code duplication, but I think it would be worth the cost.

For cases where we might throw "could not clone file between old and new data directories", I wonder if we shouldn't do some kind of dummy copy to catch that error earlier, as well.  Maybe that one is not worth it.

Cheers,

Jeff

В списке pgsql-hackers по дате отправления:

Предыдущее
От: Andres Freund
Дата:
Сообщение: Re: REINDEX INDEX results in a crash for an index of pg_class since9.6
Следующее
От: Arthur Zakirov
Дата:
Сообщение: Re: to_timestamp docs