Thread: psql crashes postmaster

psql crashes postmaster

From
pgsql-bugs@postgresql.org
Date:
Krzysztof Czuma (czuma@Elektron.pl) reports a bug with a severity of 2
The lower the number the more severe it is.

Short Description
psql crashes postmaster

Long Description
PostgreSQL 7.0.3, SunOS amber 5.8 Generic_108529-05 i86pc i386 i86pc
gcc version 2.95.2

postmaster crashes every time a user tries to access database from psql

Sample Code
psql
Password:
psql: pqReadData() -- backend closed the channel unexpectedly.
        This probably means the backend terminated abnormally
        before or while processing the request.
psql
psql: connectDBStart() -- connect() failed: No such file or directory
        Is the postmaster running at 'localhost'
        and accepting connections on Unix socket '5432'?

No file was uploaded with this report

Re: psql crashes postmaster

From
Tom Lane
Date:
pgsql-bugs@postgresql.org writes:
> postmaster crashes every time a user tries to access database from psql

Does it fail for all users, or just some?  Did it used to work and is
now failing, or is this a new installation that's never worked?

What shows up in the postmaster log when this happens?  (If you're not
running with a postmaster log, reconsider that.)  Is there a core file
left behind, and if so what does gdb show for the backtrace?

            regards, tom lane

Re: psql crashes postmaster

From
Krzysztof Czuma
Date:
Hello,

On Sun, 25 Feb 2001, Tom Lane wrote:

> pgsql-bugs@postgresql.org writes:
> > postmaster crashes every time a user tries to access database from psql
>
> Does it fail for all users, or just some?

For one user. I deleted user and this database and created them again. Now
it works.


> Did it used to work and is
> now failing, or is this a new installation that's never worked?

I am not sure when the user started to use his database. He claimed, he
has been using the database one month.


> What shows up in the postmaster log when this happens?  (If you're not
> running with a postmaster log, reconsider that.)

I tried to find how to read pg_log but I failed. :)


Kind regards,
Krzysztof Czuma