From: | Andres Freund <andres(at)anarazel(dot)de> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Jordan Deitch <jd(at)rsa(dot)pub>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: add the source of param misconfigurations to error messages |
Date: | 2018-11-13 22:42:27 |
Message-ID: | 20181113224227.awvsopcv6t7sqidy@alap3.anarazel.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
On 2018-11-13 17:33:01 -0500, Tom Lane wrote:
> Jordan Deitch <jd(at)rsa(dot)pub> writes:
> > $ postgres --config-file="/etc/postgresql/10/main/postgresql.conf"
> > can fail with the following error:
> > postgres: superuser_reserved_connections must be less than max_connections
>
> > This is due to the addition of the postgresql.auto.conf params.
> > Would the community welcome a patch whereby this detail in contained in the error?
>
> Seems to me it'd result in an impossibly unwieldy message, especially
> once you realize you might have to deal with other value sources than
> files. Adhering to the translatability guidelines (ie, "don't construct
> messages out of parts") would be problematic for that too.
Note that I'm convinced this is a necessary feature. But if we were to
do it, I'd assume we put something like this in the DETAIL not the
ERROR itself. That ought to alievate some of those concerns?
> We already have fairly substantial support for diagnosing such mistakes
> through the pg_file_settings view, though admittedly if you don't use
> that *before* restarting the server, it does not help with this.
Would be kind of useful if --describe-config, or a version thereof,
would print that kind of information too.
Greetings,
Andres Freund
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2018-11-13 23:01:46 | Re: add the source of param misconfigurations to error messages |
Previous Message | Andres Freund | 2018-11-13 22:33:30 | Re: [PATCH] Pass COPT and PROFILE to CXXFLAGS as well |