Sorry. Don't think I got that uploaded on the last message.
Scott Felt wrote:
>
> Thanks, Tom. I will alter the config file to give greater details as you
> suggest. Perhaps that will be sufficiently informative to point me toward
> a fix. Thank you.
>
> --Scott
>
>
> Tom Lane-2 wrote:
Thanks. I altered the log log_statements and added the PID to the
log_line_prefix. I have uploaded the log. Forgive me if I'm missing
something obvious here, but I do not see that PID referenced elsewhere. Is
there a a "crash report" somewhere or is that just these logs?
Thank you.
Scott
T
Looks like your typical backend crash of PID 9644, causing a typical
restart. So something broke the backend - I'd start by trying to
figure that out.
Clearly, it's failing to restart after the crash, due to shared memory
issues. At the risk of repeating, this often happens with antivirus on
the
On 19/11/2009 1:23 AM, Scott Felt wrote:
>
> Hello. I have been having an issue with a database. The logs consistently
> show this:
[snip]
> Prior to this, the logs show nothing other than AutoVacWorkerMain
> activities. This database is installed on a Windows OS. The version of
> PostgreSQL
Thanks, Tom. I will alter the config file to give greater details as you
suggest. Perhaps that will be sufficiently informative to point me toward a
fix. Thank you.
--Scott
Tom Lane-2 wrote:
>
> Scott Felt writes:
>> Hello. I have been having an issue with a database. The logs
>> consist
Scott Felt writes:
> Hello. I have been having an issue with a database. The logs consistently
> show this:
> 2009-11-17 16:03:55 ESTLOG: 0: server process (PID 9644) exited with
> exit code 128
This looks like a fairly garden-variety backend crash, but with only
this much information t
Magnus, any thoughts?
On Wed, Nov 18, 2009 at 9:53 AM, Scott Felt wrote:
>
> Hello. I have been having an issue with a database. The logs consistently
> show this:
>
> 2009-11-17 16:03:55 ESTLOG: 0: server process (PID 9644) exited with
> exit code 128
> 2009-11-17 16:03:55 ESTLOCATION:
