Wording adjusted and applied with attached patch.
---
Gurjeet Singh wrote:
> On Mon, Jun 30, 2008 at 7:33 PM, Tom Lane <[EMAIL PROTECTED]> wrote:
>
> > Alvaro Herrera <[EMAIL PROTECTED]> writes:
> > > In any case, this seem
On Mon, Jun 30, 2008 at 7:33 PM, Tom Lane <[EMAIL PROTECTED]> wrote:
> Alvaro Herrera <[EMAIL PROTECTED]> 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_buffe
Alvaro Herrera <[EMAIL PROTECTED]> 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 ch
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_buffer
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> 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 mes
Bruce Momjian <[EMAIL PROTECTED]> 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 rephra
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 SIGHU
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
