From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
Cc: | richard(at)xentu(dot)com, "pgsql-novice(at)postgresql(dot)org" <pgsql-novice(at)postgresql(dot)org> |
Subject: | Re: can't get pg_stat_statements to work |
Date: | 2015-09-19 17:30:55 |
Message-ID: | 14031.1442683855@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
"David G. Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> writes:
> On Sat, Sep 19, 2015 at 12:29 PM, <richard(at)xentu(dot)com> wrote:
>> Is that the file that gets generated in
>> /var/lib/postgresql/8.4/main/pg_log?
> I'm not sure what this ancient and no longer supported (by this community
> at least...) version of PostgreSQL does on Ubuntu but my unaltered 9.3
> installation on 14.04 places the log file into "/var/log/postgresql". I
> suspect yours does the same.
The pg_log file is probably capturing the server's original stderr output,
which would only receive error messages emitted before the server adopts
the log destination commanded by the log-related settings specified in
postgresql.conf. I believe that shared_preload_libraries is processed
after we adopt the log-related configuration settings, so whatever error
is getting reported about that would go where your configuration says.
(More recent versions than 8.4 try to leave a breadcrumb trail,
ie the last thing sent to the pg_log file would've been a hint
about where future error messages would go ...)
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | richard | 2015-09-19 17:54:06 | Re: can't get pg_stat_statements to work |
Previous Message | David G. Johnston | 2015-09-19 16:55:01 | Re: can't get pg_stat_statements to work |