| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | Mark Dilger <mark(dot)dilger(at)enterprisedb(dot)com> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: multi-install PostgresNode fails with older postgres versions |
| Date: | 2021-03-30 22:12:48 |
| Message-ID: | 20210330221248.GA10772@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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")
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2021-03-30 22:13:45 | Re: making update/delete of inheritance trees scale better |
| Previous Message | Daniel Gustafsson | 2021-03-30 21:59:17 | Re: Refactor SSL test framework to support multiple TLS libraries |