Ok - more info
I turned on connection logging a few other things, and normaly I get
something like this:
LOG: 00000: connection authorized: user=postgres database=trend
LOCATION: BackendInitialize, postmaster.c:3097
LOG: 00000: disconnection: session time: 0:00:00.004 user=postgres
database=trend host=localhost port=51586
but when it fails, I get nothing in the log at all...
ALex
On Thu, Mar 6, 2008 at 4:09 PM, Alex Turner <armtuk@gmail.com> wrote:
> Sometimes I'm getting LOG: unexptected EOF on client connection
>
> Alex
>
>
>
> On Thu, Mar 6, 2008 at 4:06 PM, Alex Turner <armtuk@gmail.com> wrote:
> > Ok - the connection closed thing is happening a lot, but not much is
> > going into pg_log...
> >
> > Alex
> >
> >
> >
> > On Thu, Mar 6, 2008 at 4:03 PM, Douglas McNaught <doug@mcnaught.org> wrote:
> > > On 3/6/08, Alex Turner <armtuk@gmail.com> wrote:
> > > > Ok - lookint at the pg log, it appears that the server process is seg
> > > > faulting :(. This might conceivably be my fault. I have 3 stored
> > > > procedures written in C, but they've been on the server for months,
> > > > and unless I didn't deploy them correctly originally I don't think
> > > > it's them.
> > > >
> > > > I'm thinking I need a core file. I'm guessing I just restart
> > > > postgresql from a user whos core file size limit is set to non zero?
> > >
> > > Or just put a 'ulimit' statement in the script that starts PG, or edit
> > > /etc/security/limits.conf if you're on RedHat.
> > >
> > > -Doug
> > >
> >
>
