From: | Mike G <mike(at)thegodshalls(dot)com> |
---|---|
To: | Daniel Baughman <danrb(at)codenet(dot)net> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: PGSQL service dieing... |
Date: | 2004-06-22 00:50:38 |
Message-ID: | 20040622005038.GA5085@localhost.localdomain |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
What version and what platform is this on?
On Fri, Jun 18, 2004 at 01:33:43PM -0600, Daniel Baughman wrote:
> My pgsql service keeps dieing and has a bunch of errors like this in the
> server log, eventually it stops giving these
>
>
> Warning: terminatin connection because of crash of another server process
> Detail: The postmaster has commanded this server process to roll back the
> current transaction and exit, because nother server process exited
> abnormally and possible corrupted shared memory
> Hint: ina moment you should be able to reconnect to the database and repeat
> your command
>
>
> And starts giving these:
>
> FATAL: the database system is in recovery mode
>
>
>
>
> Could a series of commands, say perhaps a few hundred of the course of an
> hour, that had incorrect syntax cause a problem like this? Is there
> anywhere I can go for more info?
>
> Dan
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 9: the planner will ignore your desire to choose an index scan if your
> joining column's datatypes do not match
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2004-06-22 00:52:53 | Re: Possible SET SESSION AUTHORIZATION bug |
Previous Message | Scott Marlowe | 2004-06-21 22:34:44 | Re: virtual fields on VIEW? |