Re: multi-install PostgresNode fails with older postgres versions
От | Alvaro Herrera |
---|---|
Тема | Re: multi-install PostgresNode fails with older postgres versions |
Дата | |
Msg-id | 20210330221248.GA10772@alvherre.pgsql обсуждение исходный текст |
Ответ на | multi-install PostgresNode fails with older postgres versions (Mark Dilger <mark.dilger@enterprisedb.com>) |
Ответы |
Re: multi-install PostgresNode fails with older postgres versions
|
Список | pgsql-hackers |
On 2021-Mar-30, Mark Dilger wrote: > The problem is clear enough; -N/--nosync was added in 9.3, and > PostgresNode::init is passing -N to initdb unconditionally. I wonder > if during PostgresNode::new a call should be made to pg_config and the > version information grep'd out so that version specific options to > various functions (init, backup, etc) could hinge on the version of > postgres being used? Yeah, I think making it backwards-compatible would be good. Is running pg_config to obtain the version the best way to do it? I'm not sure -- what other ways are there? I can't of anything. (Asking the user seems right out.) -- Álvaro Herrera 39°49'30"S 73°17'W Officer Krupke, what are we to do? Gee, officer Krupke, Krup you! (West Side Story, "Gee, Officer Krupke")
В списке pgsql-hackers по дате отправления: