psql leaking? - Mailing list pgsql-general

From Russ Brown
Subject psql leaking?
Date
Msg-id opsds8bicvg2z5qo@relay.plus.net
Whole thread Raw
Responses Re: psql leaking?
List pgsql-general
Hello,

Today I tried connecting to my database locally via psql. I got the usual
welcome & basic help messages, but it never got to the prompt: it just
hung. So I checked top and the psql process was increasing in size at
quite a rate (up to a gig in under 30 seconds).

I'd been using psql with no problems only a couple of hours ago, and I
haven't installed anything for at least a couple of days that I can think
of.

The first thing I did was to pg_dumpall a backup and try recompiling the
server. That didn't work, so I tried doing initdb again. No joy. So I
upgraded to 7.4.5 (was 7.4.3 before), and again no joy. Note that it
happens just after I've run initdb, so even when my database has gone
nowhere near it: this is effectively a clean compile and install that is
failing at this point.

I've turned logging up full and got this (starting from when I run the
psql command):

2004-09-04 16:43:29 DEBUG:  forked new backend, pid=23315 socket=8
2004-09-04 16:43:29 DEBUG:  /usr/bin/postmaster child[23315]: starting
with (
2004-09-04 16:43:29 DEBUG:      postgres
2004-09-04 16:43:29 DEBUG:      -v196608
2004-09-04 16:43:29 DEBUG:      -p
2004-09-04 16:43:29 DEBUG:      template1
2004-09-04 16:43:29 DEBUG:  )
2004-09-04 16:43:29 DEBUG:  InitPostgres
2004-09-04 16:44:53 LOG:  unexpected EOF on client connection
2004-09-04 16:44:53 DEBUG:  proc_exit(0)
2004-09-04 16:44:53 DEBUG:  shmem_exit(0)
2004-09-04 16:44:53 DEBUG:  exit(0)
2004-09-04 16:44:53 DEBUG:  reaping dead processes
2004-09-04 16:44:53 DEBUG:  child process (PID 23315) exited with exit
code 0

The LOG is the point at which I CTRL+C the client.

I'm suspecting that there's a problem with one of the libraries that psql
uses: I really can't see this being a psql bug as I'd have noticed it
before: there must be something else going on. Trouble is, I don't know
what libraries it uses other than glibc (which I'm currently recompiling
just in case).

I'm at a loss, and can't think of anything else. This has just happened
totally unprompted and without any real clues that I can see.

Anyone else have any ideas?

Thanks.

--

  Russell Brown

pgsql-general by date:

Previous
From: Lincoln Yeoh
Date:
Subject: Re: postgres "on in the internet"
Next
From: "Jim Wilson"
Date:
Subject: Re: "echo"ing a psql command in a bash script