pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Albert REINER <areiner@tph.tuwien.ac.at>
Cc: PostgreSQL-SQL <pgsql-sql@postgreSQL.org>
Subject: Re: [SQL] Can VACUUM, but cannot do VACUUM ANALYZE
Date: Sat, 23 Oct 1999 12:18:33 -0400
Message-ID: <1391.940695513@sss.pgh.pa.us> (raw)
In-Reply-To: <19991023091819.C833@frithjof>

"Albert REINER" <areiner@tph.tuwien.ac.at> writes:
>> albert=> vacuum analyze;
>> NOTICE:  AbortTransaction and not in in-progress state
>> pqReadData() -- backend closed the channel unexpectedly.

This unhelpful trace is the result of the interaction of a couple
of different bugs --- first, vacuum is encountering some sort of
error; then error recovery is messing up in the context of vacuum
(leading first to the NOTICE and then to the coredump); and when
libpq observes connection closure, it drops the original error
message (which it has already received!) on the floor in its haste
to tell you about the closed connection.

The error recovery problem is fixed as of 6.5.2, I believe, so it'd
be worth your while to upgrade.  The libpq misbehavior is fixed for
7.0, but it's part of some extensive changes that seemed too risky
to back-patch into 6.5.*.  In the meantime, the only way to find out
what that original error message was is to consult the postmaster log
file --- you are running the postmaster with stdout/stderr going to
some logfile, I hope.  It should show up right before the NOTICE and
then the postmaster's response to the backend coredump.

Once we have vacuum's error message we can maybe offer some useful
counsel.

			regards, tom lane



view thread (8+ messages)  latest in thread

Message-ID: <1391.940695513@sss.pgh.pa.us>
Permalink:  ../1391.940695513@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/1391.940695513@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-sql@postgresql.org
  Cc: tgl@sss.pgh.pa.us, areiner@tph.tuwien.ac.at
  Subject: Re: [SQL] Can VACUUM, but cannot do VACUUM ANALYZE
  In-Reply-To: <1391.940695513@sss.pgh.pa.us>
  References: <19991023091819.C833@frithjof> <1391.940695513@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