Tom Lane wrote:
> Kevin Grittner writes:
>> My preference would be to not generate noise for interim states;
>> just report net changes.
>
> Yeah. Is it worth explicitly detecting and dropping redundant assignments
> to the same variable? A naive check for that would be O(N^2) in the
> number o
Kevin Grittner writes:
> My preference would be to not generate noise for interim states;
> just report net changes.
Yeah. Is it worth explicitly detecting and dropping redundant assignments
to the same variable? A naive check for that would be O(N^2) in the
number of entries in the conf file,
On 2014-01-22 12:10:30 -0500, Tom Lane wrote:
> Kevin Grittner writes:
> > My preference would be to not generate noise for interim states;
> > just report net changes.
>
> Yeah. Is it worth explicitly detecting and dropping redundant assignments
> to the same variable? A naive check for that w
Andres Freund wrote:
> A rather common and sensible configuration is to have a common
> configuration file used across servers, which then is overwritten
> by a per-server or per-cluster config file containing values
> specific to a server/cluster.
Agreed.
My preference would be to not generate
On 2014-01-21 16:13:11 -0500, Robert Haas wrote:
> On Tue, Jan 21, 2014 at 3:37 PM, Tom Lane wrote:
> > Robert Haas writes:
> >> I kind of agree with Thom. I understand why it's doing what it's
> >> doing, but it still seems sort of lame.
> >
> > Well, the point of the message is to report that
On 01/21/2014 12:29 PM, Robert Haas wrote:
On Tue, Jan 21, 2014 at 1:59 PM, Thom Brown wrote:
On 21 January 2014 18:35, Tom Lane wrote:
Thom Brown writes:
I'm getting a report of a config error when changing a config value
that requires a restart:
...
2014-01-21 18:14:53 GMT [28718]: [4-1]
Robert Haas writes:
> The only real argument for the message:
> LOG: configuration file "/home/thom/Development/data/postgresql.conf"
> contains errors; unaffected changes were applied
> ...is that somebody might think that the presence of a single error
> caused all the changes to be ignored.
On Tue, Jan 21, 2014 at 3:37 PM, Tom Lane wrote:
> Robert Haas writes:
>> I kind of agree with Thom. I understand why it's doing what it's
>> doing, but it still seems sort of lame.
>
> Well, the point of the message is to report that we failed to apply
> all the settings requested by the file.
Robert Haas writes:
> I kind of agree with Thom. I understand why it's doing what it's
> doing, but it still seems sort of lame.
Well, the point of the message is to report that we failed to apply
all the settings requested by the file. If you prefer some wording
squishier than "error", we coul
On Tue, Jan 21, 2014 at 1:59 PM, Thom Brown wrote:
> On 21 January 2014 18:35, Tom Lane wrote:
>> Thom Brown writes:
>>> I'm getting a report of a config error when changing a config value
>>> that requires a restart:
>>> ...
>>> 2014-01-21 18:14:53 GMT [28718]: [4-1] user=,db=,client= LOG:
>>>
On 21 January 2014 18:35, Tom Lane wrote:
> Thom Brown writes:
>> I'm getting a report of a config error when changing a config value
>> that requires a restart:
>> ...
>> 2014-01-21 18:14:53 GMT [28718]: [4-1] user=,db=,client= LOG:
>> received SIGHUP, reloading configuration files
>> 2014-01-21
On 01/21/2014 10:26 AM, Thom Brown wrote:
Hi all,
I'm getting a report of a config error when changing a config value
that requires a restart:
In postgresql.conf
max_connections = 92
(pg_ctl restart)
postgres=# show max_connections ;
max_connections
-
92
(1 row)
(Edit
Thom Brown writes:
> I'm getting a report of a config error when changing a config value
> that requires a restart:
> ...
> 2014-01-21 18:14:53 GMT [28718]: [4-1] user=,db=,client= LOG:
> received SIGHUP, reloading configuration files
> 2014-01-21 18:14:53 GMT [28718]: [5-1] user=,db=,client= LOG:
Hi all,
I'm getting a report of a config error when changing a config value
that requires a restart:
In postgresql.conf
max_connections = 92
(pg_ctl restart)
postgres=# show max_connections ;
max_connections
-
92
(1 row)
(Edit postgresql.conf so that max_connections = 93)
14 matches
Mail list logo
