pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Gordon Ross <G.Ross@ccw.gov.uk>
Cc: pgsql-admin@postgresql.org
Subject: Re: Problems dumping database from 7.3.1
Date: Wed, 12 May 2004 09:10:36 -0400
Message-ID: <24210.1084367436@sss.pgh.pa.us> (raw)
In-Reply-To: <s0a21be7.090@groupwise.ccw.gov.uk>
References: <s0a21be7.090@groupwise.ccw.gov.uk>

"Gordon Ross" <G.Ross@ccw.gov.uk> writes:
> I've been using a PGSQL 7.3.1 system as my development box for some time, and so far, it worked fine. (This is running on Slackware distro with a 2.2.19 kernel under VMWare 4)
> However, yesterday, I added a column to a base table (that is inherited by several other tables). Shortly afterwards, whenever I tried to access either the base table or child tables, I get the message saying that pgsql has lost communication with the server.

Sounds pretty messy.  If you're really lucky, an in-place update to
7.3.6 might fix it, but I can't offhand think of any bug fixes in the
7.3.* branch that had anything to do with inheritance.

Of course it's not necessarily true that this has anything to do with
inheritance, either.  What we'd need to know before we could speculate
much further is where exactly the crash is happening.  A gdb backtrace
from the SEGV would help a lot.  I'd suggest:

1. Start a psql session.  Figure out the PID of the connected backend
(pg_stat_activity may help, or just use "ps").

2. In another shell window, attach to the backend process with gdb:
	gdb /path/to/postgres-executable PID
	...
	gdb>
(You can do this either as root or as the postgres user.)

3. Tell gdb to let the backend continue:
	gdb> cont

4. Do whatever it takes in the psql session to provoke crash.  gdb
should announce that the backend has gotten a signal 11.  Now say
	gdb> bt
	gdb> quit

and send along the output of bt.

			regards, tom lane



view thread (7+ messages)  latest in thread

Message-ID: <24210.1084367436@sss.pgh.pa.us>
Permalink:  ../24210.1084367436@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/24210.1084367436@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: tgl@sss.pgh.pa.us, G.Ross@ccw.gov.uk
  Subject: Re: Problems dumping database from 7.3.1
  In-Reply-To: <24210.1084367436@sss.pgh.pa.us>
  References: <s0a21be7.090@groupwise.ccw.gov.uk> <24210.1084367436@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox