Re: multi-install PostgresNode fails with older postgres versions
От | Andrew Dunstan |
---|---|
Тема | Re: multi-install PostgresNode fails with older postgres versions |
Дата | |
Msg-id | a972a924-d850-278e-f415-62ab1c9bbaaa@dunslane.net обсуждение исходный текст |
Ответ на | Re: multi-install PostgresNode fails with older postgres versions (Michael Paquier <michael@paquier.xyz>) |
Ответы |
Re: multi-install PostgresNode fails with older postgres versions
Re: multi-install PostgresNode fails with older postgres versions |
Список | pgsql-hackers |
On 4/21/21 1:13 AM, Michael Paquier wrote: > On Tue, Apr 20, 2021 at 01:11:59PM -0400, Andrew Dunstan wrote: >> Here's the patch for that. > Thanks. > >> + # Accept standard formats, in case caller has handed us the output of a >> + # postgres command line tool >> + $arg = $1 >> + if ($arg =~ m/\(?PostgreSQL\)? (\d+(?:\.\d+)*(?:devel)?)/); > Interesting. This would work even if using --with-extra-version, > which is a good thing. > >> +# render the version number in the standard "joined by dots" notation if >> +# interpolated into a string >> +sub _stringify >> +{ >> + my $self = shift; >> + return join('.', @$self); >> +} > This comes out a bit strangely when using a devel build as this > appends -1 as sub-version number, becoming say 14.-1. It may be > clearer to add back "devel" in this case? > > Wouldn't it be better to add some perldoc to PostgresVersion.pm? Here's a patch with these things attended to. cheers andrew -- Andrew Dunstan EDB: https://www.enterprisedb.com
Вложения
В списке pgsql-hackers по дате отправления: