Re: [GENERAL] FATAL: could not read statistics message

2006-05-17 Thread Jim C. Nasby
On Tue, May 16, 2006 at 07:24:43PM -0400, Sean Davis wrote: > Jim C. Nasby wrote: > >On Tue, May 16, 2006 at 03:41:07PM -0400, Sean Davis wrote: > > > >>I had cranked things up a bit from the standard install. > >> > >>shared_buffers = 15000 # min 16 or max_connections*2, 8KB > >>e

Re: [GENERAL] FATAL: could not read statistics message

2006-05-16 Thread Sean Davis
Tony Wasson wrote: On 5/16/06, Tom Lane <[EMAIL PROTECTED]> wrote: "Tony Wasson" <[EMAIL PROTECTED]> writes: > When I saw the same error as you, the stats collector process was > missing. The collector, or the buffer process? The reported message would be emitted by the buffer process, after

Re: [GENERAL] FATAL: could not read statistics message

2006-05-16 Thread Tony Wasson
On 5/16/06, Tom Lane <[EMAIL PROTECTED]> wrote: "Tony Wasson" <[EMAIL PROTECTED]> writes: > When I saw the same error as you, the stats collector process was > missing. The collector, or the buffer process? The reported message would be emitted by the buffer process, after which it would immedi

Re: [GENERAL] FATAL: could not read statistics message

2006-05-16 Thread Sean Davis
Jim C. Nasby wrote: On Tue, May 16, 2006 at 03:41:07PM -0400, Sean Davis wrote: I had cranked things up a bit from the standard install. shared_buffers = 15000 # min 16 or max_connections*2, 8KB each #temp_buffers = 1000# min 100, 8KB each #max_prepared_t

Re: [GENERAL] FATAL: could not read statistics message

2006-05-16 Thread Tom Lane
"Tony Wasson" <[EMAIL PROTECTED]> writes: > When I saw the same error as you, the stats collector process was > missing. The collector, or the buffer process? The reported message would be emitted by the buffer process, after which it would immediately exit. (The collector would go away too once

Re: [GENERAL] FATAL: could not read statistics message

2006-05-16 Thread Tony Wasson
On 5/16/06, Sean Davis <[EMAIL PROTECTED]> wrote: I had cranked things up a bit from the standard install. shared_buffers = 15000 # min 16 or max_connections*2, 8KB each #temp_buffers = 1000# min 100, 8KB each #max_prepared_transactions = 50 # can be

Re: [GENERAL] FATAL: could not read statistics message

2006-05-16 Thread Jim C. Nasby
On Tue, May 16, 2006 at 03:41:07PM -0400, Sean Davis wrote: > I had cranked things up a bit from the standard install. > > shared_buffers = 15000 # min 16 or max_connections*2, 8KB > each > #temp_buffers = 1000# min 100, 8KB each > #max_prepared_transactions =

Re: [GENERAL] FATAL: could not read statistics message

2006-05-16 Thread Sean Davis
On 5/16/06 3:08 PM, "Tony Wasson" <[EMAIL PROTECTED]> wrote: > On 5/16/06, Sean Davis <[EMAIL PROTECTED]> wrote: >> I am using postgresql 8.1.0 on an Xserver running MacOS 10.3.9. I am >> getting the following in the log every minute for the past couple of days. >> The database is otherwise ru

Re: [GENERAL] FATAL: could not read statistics message

2006-05-16 Thread Tony Wasson
On 5/16/06, Sean Davis <[EMAIL PROTECTED]> wrote: I am using postgresql 8.1.0 on an Xserver running MacOS 10.3.9. I am getting the following in the log every minute for the past couple of days. The database is otherwise running normally, as far as I can tell: 2006-05-16 07:26:01 EDT FATAL: c