Lists: | pgsql-hackers |
---|
From: | "Gurjeet Singh" <singh(dot)gurjeet(at)gmail(dot)com> |
---|---|
To: | "PGSQL Hackers" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Confusing message in log file |
Date: | 2008-05-15 04:43:43 |
Message-ID: | 65937bea0805142143k12cd09hc75e0466f261106b@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Lists: | pgsql-hackers |
Hi All,
I changed the postgresql.conf file (of an 8.2.4 server), and issued
relaod using pg_reload_config(). Following are the messages I see in the log
files:
May 14 21:38:40 sfphotodb001 postgres[29658]: [19-1] 2008-05-14 21:38:40
PDTLOG: received SIGHUP, reloading configuration files
May 14 21:38:40 sfphotodb001 postgres[29658]: [20-1] 2008-05-14 21:38:40
PDTLOG: parameter "shared_buffers" cannot be changed after server start;
configuration file change ignored
May 14 21:39:03 sfphotodb001 postgres[22928]: [21-1] 2008-05-14 21:39:03
PDTLOG: archived transaction log file "0000000100000E23000000C8"
What's confusing about this is that the second message says
'configuration file change ignored', so I expect the changed (newly enabled)
archive_command to not take effect. But in fact, it does take effect.
The message probably should be rephrased to say that this setting
(shared_buffers) will not be changed.
Best regards,
--
gurjeet[(dot)singh](at)EnterpriseDB(dot)com
singh(dot)gurjeet(at){ gmail | hotmail | indiatimes | yahoo }.com
EnterpriseDB http://www.enterprisedb.com
Mail sent from my BlackLaptop device
From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Gurjeet Singh <singh(dot)gurjeet(at)gmail(dot)com> |
Cc: | PGSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Confusing message in log file |
Date: | 2008-06-30 22:43:06 |
Message-ID: | 200806302243.m5UMh6u18724@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Lists: | pgsql-hackers |
Gurjeet Singh wrote:
> Hi All,
>
> I changed the postgresql.conf file (of an 8.2.4 server), and issued
> relaod using pg_reload_config(). Following are the messages I see in the log
> files:
>
> May 14 21:38:40 sfphotodb001 postgres[29658]: [19-1] 2008-05-14 21:38:40
> PDTLOG: received SIGHUP, reloading configuration files
> May 14 21:38:40 sfphotodb001 postgres[29658]: [20-1] 2008-05-14 21:38:40
> PDTLOG: parameter "shared_buffers" cannot be changed after server start;
> configuration file change ignored
> May 14 21:39:03 sfphotodb001 postgres[22928]: [21-1] 2008-05-14 21:39:03
> PDTLOG: archived transaction log file "0000000100000E23000000C8"
>
>
> What's confusing about this is that the second message says
> 'configuration file change ignored', so I expect the changed (newly enabled)
> archive_command to not take effect. But in fact, it does take effect.
>
> The message probably should be rephrased to say that this setting
> (shared_buffers) will not be changed.
Actually, no one else has been confused by this wording before, and I
can't think of better wording that doesn't sound redundant.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Bruce Momjian <bruce(at)momjian(dot)us> |
Cc: | Gurjeet Singh <singh(dot)gurjeet(at)gmail(dot)com>, PGSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Confusing message in log file |
Date: | 2008-06-30 22:50:21 |
Message-ID: | 7217.1214866221@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Lists: | pgsql-hackers |
Bruce Momjian <bruce(at)momjian(dot)us> writes:
> Gurjeet Singh wrote:
>> May 14 21:38:40 sfphotodb001 postgres[29658]: [20-1] 2008-05-14 21:38:40
>> PDTLOG: parameter "shared_buffers" cannot be changed after server start;
>> configuration file change ignored
>>
>> The message probably should be rephrased to say that this setting
>> (shared_buffers) will not be changed.
> Actually, no one else has been confused by this wording before, and I
> can't think of better wording that doesn't sound redundant.
How about "... after server start; change ignored" ?
Or "attempted change ignored" ?
regards, tom lane
From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Gurjeet Singh <singh(dot)gurjeet(at)gmail(dot)com>, PGSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Confusing message in log file |
Date: | 2008-06-30 22:54:46 |
Message-ID: | 200806302254.m5UMskS29741@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Lists: | pgsql-hackers |
Tom Lane wrote:
> Bruce Momjian <bruce(at)momjian(dot)us> writes:
> > Gurjeet Singh wrote:
> >> May 14 21:38:40 sfphotodb001 postgres[29658]: [20-1] 2008-05-14 21:38:40
> >> PDTLOG: parameter "shared_buffers" cannot be changed after server start;
> >> configuration file change ignored
> >>
> >> The message probably should be rephrased to say that this setting
> >> (shared_buffers) will not be changed.
>
> > Actually, no one else has been confused by this wording before, and I
> > can't think of better wording that doesn't sound redundant.
>
> How about "... after server start; change ignored" ?
> Or "attempted change ignored" ?
Yea, I like "change ignored" rather than mentioning the configuration
file.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | Bruce Momjian <bruce(at)momjian(dot)us> |
Cc: | Gurjeet Singh <singh(dot)gurjeet(at)gmail(dot)com>, PGSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Confusing message in log file |
Date: | 2008-06-30 23:02:04 |
Message-ID: | 20080630230204.GD18252@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Lists: | pgsql-hackers |
Bruce Momjian escribió:
> Gurjeet Singh wrote:
> > May 14 21:38:40 sfphotodb001 postgres[29658]: [19-1] 2008-05-14 21:38:40
> > PDTLOG: received SIGHUP, reloading configuration files
> > May 14 21:38:40 sfphotodb001 postgres[29658]: [20-1] 2008-05-14 21:38:40
> > PDTLOG: parameter "shared_buffers" cannot be changed after server start;
> > configuration file change ignored
> > What's confusing about this is that the second message says
> > 'configuration file change ignored', so I expect the changed (newly enabled)
> > archive_command to not take effect. But in fact, it does take effect.
> >
> > The message probably should be rephrased to say that this setting
> > (shared_buffers) will not be changed.
>
> Actually, no one else has been confused by this wording before, and I
> can't think of better wording that doesn't sound redundant.
Perhaps this is because not enough people have seen it. I agree that
the message should specify that only this setting has been ignored.
In any case, this seems a case of stuffing too much in the primary
message. I think it should be something like
errmsg("parameter \"shared_buffer\" change in configuration file ignored"),
errdetail("This parameter cannot be changed after server start.")
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, Gurjeet Singh <singh(dot)gurjeet(at)gmail(dot)com>, PGSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Confusing message in log file |
Date: | 2008-06-30 23:33:15 |
Message-ID: | 18847.1214868795@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Lists: | pgsql-hackers |
Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> In any case, this seems a case of stuffing too much in the primary
> message.
Yeah, good point.
> I think it should be something like
> errmsg("parameter \"shared_buffer\" change in configuration file ignored"),
> errdetail("This parameter cannot be changed after server start.")
Seems a bit awkwardly phrased. I propose
errmsg("attempted change to parameter \"shared_buffer\" ignored"),
errdetail("This parameter cannot be changed after server start.")
(or possibly "of" would read better than "to")
regards, tom lane
From: | "Gurjeet Singh" <singh(dot)gurjeet(at)gmail(dot)com> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "Alvaro Herrera" <alvherre(at)commandprompt(dot)com>, "Bruce Momjian" <bruce(at)momjian(dot)us>, "PGSQL Hackers" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Confusing message in log file |
Date: | 2008-07-01 14:07:03 |
Message-ID: | 65937bea0807010707ycc1bdeckbdbf459362c066c0@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Lists: | pgsql-hackers |
On Mon, Jun 30, 2008 at 7:33 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> > In any case, this seems a case of stuffing too much in the primary
> > message.
>
> Yeah, good point.
>
> > I think it should be something like
> > errmsg("parameter \"shared_buffer\" change in configuration file
> ignored"),
> > errdetail("This parameter cannot be changed after server start.")
>
> Seems a bit awkwardly phrased. I propose
>
> errmsg("attempted change to parameter \"shared_buffer\" ignored"),
> errdetail("This parameter cannot be changed after server start.")
>
> (or possibly "of" would read better than "to")
>
>
'of' sounds better than 'to'.
Best regards,
--
gurjeet[(dot)singh](at)EnterpriseDB(dot)com
singh(dot)gurjeet(at){ gmail | hotmail | indiatimes | yahoo }.com
EnterpriseDB http://www.enterprisedb.com
Mail sent from my BlackLaptop device
From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Gurjeet Singh <singh(dot)gurjeet(at)gmail(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, PGSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Confusing message in log file |
Date: | 2008-08-22 00:04:45 |
Message-ID: | 200808220004.m7M04kR09952@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Lists: | pgsql-hackers |
Wording adjusted and applied with attached patch.
---------------------------------------------------------------------------
Gurjeet Singh wrote:
> On Mon, Jun 30, 2008 at 7:33 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> > Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> > > In any case, this seems a case of stuffing too much in the primary
> > > message.
> >
> > Yeah, good point.
> >
> > > I think it should be something like
> > > errmsg("parameter \"shared_buffer\" change in configuration file
> > ignored"),
> > > errdetail("This parameter cannot be changed after server start.")
> >
> > Seems a bit awkwardly phrased. I propose
> >
> > errmsg("attempted change to parameter \"shared_buffer\" ignored"),
> > errdetail("This parameter cannot be changed after server start.")
> >
> > (or possibly "of" would read better than "to")
> >
> >
> 'of' sounds better than 'to'.
>
> Best regards,
> --
> gurjeet[(dot)singh](at)EnterpriseDB(dot)com
> singh(dot)gurjeet(at){ gmail | hotmail | indiatimes | yahoo }.com
>
> EnterpriseDB http://www.enterprisedb.com
>
> Mail sent from my BlackLaptop device
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
Attachment | Content-Type | Size |
---|---|---|
/rtmp/diff | text/x-diff | 2.4 KB |