Re: FW: database failure.. - Mailing list pgsql-general

Ausrack Webmaster wrote:
>
> Nobody got any ideas on the below problem? :-(

 From the behaviour I would guess there is something corrupt in one of
the system catalogs of that database. Make sure the coredump size of the
postmaster process is unlimited, recreate the problem and you should
find a file named "core" in the data directory of that database.
Hopefully the postgres executable was built with enough symbol
information so that you can get a stack backtrace from that core file
with a debugger.


Jan

>
>
>
> [root /tmp]# psql -V
> psql (PostgreSQL) 7.0.2
> contains readline, history, multibyte support
> Portions Copyright (c) 1996-2000, PostgreSQL, Inc
> Portions Copyright (c) 1996 Regents of the University of California Read
> the file COPYRIGHT or use the command \copyright to see the usage and
> distribution terms.
>
> Nothing at all in the logs...How do I change the debugging/log level to
> show more?
>
> NB. a few of the DBs on the server dont have any problems at all...
>
> Jason
>
> -----Original Message-----
> From: Marc G. Fournier [mailto:scrappy@postgresql.org]
> Sent: Sunday, December 14, 2003 8:00 PM
> To: Ausrack Webmaster
> Cc: pgsql-general@postgresql.org
> Subject: Re: [GENERAL] database failure..
>
>
> On Sun, 14 Dec 2003, Ausrack Webmaster wrote:
>
>>
>> Hi,
>>
>> I have a database, which just happens to be the main database on a
>> RAQ4..(cobalt)
>> that even when recreated it still dies, even before readding any
>> tables..
>>
>> Welcome to psql, the PostgreSQL interactive terminal.
>>
>> Type:  \copyright for distribution terms
>>        \h for help with SQL commands
>>        \? for help on internal slash commands
>>        \g or terminate with semicolon to execute query
>>        \q to quit
>>
>> cobalt=# \d
>> The connection to the server was lost. Attempting reset: Succeeded.
>>
>> I can't dump either..
>>
>> getTables(): SELECT failed.  Explanation from backend: 'pqReadData()
>> -- backend closed the channel unexpectedly.
>>         This probably means the backend terminated abnormally
>>         before or while processing the request.
>> '.
>>
>> Any idea what might be causing this?
>
> anything in the logs?  hardware failure maybe?  what version of
> database?
>
> ----
> Marc G. Fournier           Hub.Org Networking Services
> (http://www.hub.org)
> Email: scrappy@hub.org           Yahoo!: yscrappy              ICQ:
> 7615664
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
>                http://www.postgresql.org/docs/faqs/FAQ.html


--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me.                                  #
#================================================== JanWieck@Yahoo.com #