Re: [PATCH] pg_ctl should not truncate command lines at 1024 characters
Ranier Vilela <ranier.vf@gmail.com>
From: Ranier Vilela <ranier.vf@gmail.com>
To: Phil Krylov <phil@krylov.eu>
Cc: Pg Hackers <pgsql-hackers@postgresql.org>
Date: 2021-09-02T22:36:08Z
Lists: pgsql-hackers
Em qui., 2 de set. de 2021 às 18:36, Phil Krylov <phil@krylov.eu> escreveu: > Hello, > > Lacking a tool to edit postgresql.conf programmatically, people resort > to passing cluster options on the command line. While passing all > non-default options in this way may sound like an abuse of the feature, > IMHO pg_ctl should not blindly truncate generated command lines at > MAXPGPATH (1024 characters) and then run that, resulting in: > The msvc docs says that limit for the command line is 32,767 characters, while ok for me, I think if not it would be better to check this limit? > /bin/sh: Syntax error: end of file unexpected (expecting word) > pg_ctl: could not start server > Examine the log output. > > The attached patch tries to fix it in the least intrusive way. > > While we're at it, is it supposed that pg_ctl is a very short-lived > process and is therefore allowed to leak memory? I've noticed some > places where I would like to add a free() call. > +1 to add free. regards, Ranier Vilela
Commits
-
Remove arbitrary MAXPGPATH limit on command lengths in pg_ctl.
- 9a070c658906 9.6.24 landed
- 6e2f4581781b 10.19 landed
- beb404d3b165 11.14 landed
- 87ad491472d6 15.0 landed
- 742b30caee65 13.5 landed
- 69d670e68ec9 14.0 landed
- 3b302eb1ea2e 12.9 landed