diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2012-06-11 22:47:16 -0400 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2012-06-11 22:47:16 -0400 |
| commit | 51e61b04f8040f627e7605594095b06c10582fd0 (patch) | |
| tree | add9df96d89ff138c20bd56ffdebf733094b3b51 /src/backend/utils/adt/json.c | |
| parent | bf0945e8636bf0390ef4569bbbf9763573211e03 (diff) | |
| download | postgresql-51e61b04f8040f627e7605594095b06c10582fd0.tar.gz postgresql-51e61b04f8040f627e7605594095b06c10582fd0.zip | |
Ensure pg_ctl behaves sanely when data directory is not specified.
Commit aaa6e1def292cdacb6b27088898793b1b879fedf introduced multiple hazards
in the case where pg_ctl is executed with neither a -D switch nor any
PGDATA environment variable. It would dump core on machines which are
unforgiving about printf("%s", NULL), or failing that possibly give a
rather unhelpful complaint about being unable to execute "postgres -C",
rather than the logically prior complaint about not being told where the
data directory is.
Edmund Horner's report suggests that there is another, Windows-specific
hazard here, but I'm not the person to fix that; it would in any case only
be significant when trying to use a config-only PGDATA pointer.
Diffstat (limited to 'src/backend/utils/adt/json.c')
0 files changed, 0 insertions, 0 deletions