From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: nicer error out in initdb? |
Date: | 2006-01-05 15:54:44 |
Message-ID: | 18054.1136476484@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> If we find at the bottom of test_config_settings() that we have not been
> able to run successfully at all (i.e. status != 0 at about line 1183 of
> initdb.c) is there any point in continuing? Don't we know that we are
> bound to fail at the template1 creation stage? Maybe we should just exit
> nicely when we do know this.
Nope: since we've been suppressing stderr, "exit nicely" here would
translate as "refuse to provide any information about the problem".
The existing behavior is just fine.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2006-01-05 16:04:14 | Re: postmaster/postgres options assimilation plan |
Previous Message | Rod Taylor | 2006-01-05 15:40:35 | Re: [PATCHES] TRUNCATE, VACUUM, ANALYZE privileges |