Re: Avoiding Tablespace path collision for primary and standby

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: Avoiding Tablespace path collision for primary and standby
Дата
Msg-id 4751.1527258832@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Avoiding Tablespace path collision for primary and standby  (Ashwin Agrawal <aagrawal@pivotal.io>)
Ответы Re: Avoiding Tablespace path collision for primary and standby  (Ashwin Agrawal <aagrawal@pivotal.io>)
Список pgsql-hackers
Ashwin Agrawal <aagrawal@pivotal.io> writes:
> Proposing to create directory with timestamp at time of creating tablespace
> and create symbolic link to it instead.

I'm skeptical that this solves your problem.  What happens when the CREATE
TABLESPACE command is replicated to the standby with sub-second delay?
Clock skew is another reason to doubt that timestamp == unique identifier,
which is essentially what you're assuming here.

Even if we fixed that, the general idea of including a quasi-random
component in the directory name seems like it would have a lot of
unpleasant side effects in terms of reproduceability, testability, etc.

            regards, tom lane


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

Предыдущее
От: Robert Haas
Дата:
Сообщение: Re: Enhancement Idea - Expose the active value of a parameter in pg_settings
Следующее
От: Tom Lane
Дата:
Сообщение: Re: Unexpected casts while using date_trunc()