On 06/13/13 20:44, Jeff Frost wrote:
> These are definitely busy systems, but usually not running close to the edge,
> I'll see if I can make a test case using pgbench on 9.2.4.
I'm afraid my attempts to reproduce were again unsuccessful.
:-(
--
Sent via pgsql-bugs mailing list (pgsql-bugs@
On Jun 13, 2013, at 7:48 PM, Tom Lane wrote:
> Jeff Frost writes:
>> What I don't understand is the new log file being created from the new
>> log_filename setting but then nothing being logged into it. Is it the
>> postmaster which creates that file? I would've thought it would be
>> the log
Jeff Frost writes:
> What I don't understand is the new log file being created from the new
> log_filename setting but then nothing being logged into it. Is it the
> postmaster which creates that file? I would've thought it would be
> the logger process?
Hm, I hadn't focused on that --- that *i
On Jun 13, 2013, at 5:16 PM, Tom Lane wrote:
> Jeff Frost writes:
>> On Jun 13, 2013, at 4:50 PM, Tom Lane wrote:
>>> ... So one theory about this would be that those processes
>>> aren't absorbing the GUC updates, perhaps because the SIGHUP signals the
>>> postmaster should be sending them a
Tom Lane wrote:
> j...@pgexperts.com writes:
> > What happens is that we change various logging options in postgresql.conf,
> > then reload, and every so often, the settings don't seem to take effect even
> > though they are logged as being changed.
>
> FWIW, the "parameter changed" messages are l
Jeff Frost writes:
> On Jun 13, 2013, at 4:50 PM, Tom Lane wrote:
>> ... So one theory about this would be that those processes
>> aren't absorbing the GUC updates, perhaps because the SIGHUP signals the
>> postmaster should be sending them are getting lost.
> Interestingly, it will often pick
On Jun 13, 2013, at 4:50 PM, Tom Lane wrote:
> j...@pgexperts.com writes:
>> What happens is that we change various logging options in postgresql.conf,
>> then reload, and every so often, the settings don't seem to take effect even
>> though they are logged as being changed.
>
> FWIW, the "para
j...@pgexperts.com writes:
> What happens is that we change various logging options in postgresql.conf,
> then reload, and every so often, the settings don't seem to take effect even
> though they are logged as being changed.
FWIW, the "parameter changed" messages are logged when the postmaster
pr
On 06/11/13 15:27, j...@pgexperts.com wrote:
> The following bug has been logged on the website:
>
> Bug reference: 8225
> Logged by: Jeff Frost
> Email address: j...@pgexperts.com
> PostgreSQL version: 9.1.8
> Operating system: various
> Description:
>
> I've seen this
The following bug has been logged on the website:
Bug reference: 8225
Logged by: Jeff Frost
Email address: j...@pgexperts.com
PostgreSQL version: 9.1.8
Operating system: various
Description:
I've seen this a few times on client servers but still can't seem to boil it
10 matches
Mail list logo
