pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Oliver Elphick <olly@lfix.co.uk>
To: phd2@earthling.net
Cc: Albert REINER <areiner@tph.tuwien.ac.at>
Cc: PostgreSQL-SQL <pgsql-sql@postgreSQL.org>
Cc: olly@linda.lfix.co.uk
Subject: Re: [SQL] Can VACUUM, but cannot do VACUUM ANALYZE
Date: Sat, 23 Oct 1999 14:59:26 +0100
Message-ID: <199910231359.OAA30607@linda.lfix.co.uk> (raw)
In-Reply-To: <phd@phd.russ.ru> <Pine.LNX.4.20.9910231202050.9896-100000@fep132.fep.ru>
References: <Pine.LNX.4.20.9910231202050.9896-100000@fep132.fep.ru>

Oleg Broytmann wrote:
  >On Sat, 23 Oct 1999, Albert REINER wrote:
  >> I.e., I can VACUUM, but I cannot do VACUUM ANALYZE. Why should analyze
  >> do an ABORT? By the way, I do not notice any strange behavior with
  >> this database, and pg_dump works fine on it.
  >
  >   Once I saw similar behaviour. I found thta the problem was in broken
  >strcoll() function in glibc2; I compiled Postgres with locale support.
  >After upgrading (Debain GNU/Linux 2.0 to 2.1) I got newer libc, and the
  >problem gone away.
  >   What system/config you are running? OS, compiler, postgres version,
  >compilation flags?

There was also a specific vacuum analyze bug in vc_abort, fixed in 6.5.2.
The error log showed something like

ERROR:  vacuum: can't destroy lock file!
NOTICE:  AbortTransaction and not in in-progress state

See the pgsql-hackers archive around 10th and 13th August.

-- 
      Vote against SPAM: http://www.politik-digital.de/spam/
                 ========================================
Oliver Elphick                                Oliver.Elphick@lfix.co.uk
Isle of Wight                              http://www.lfix.co.uk/oliver
               PGP key from public servers; key ID 32B8FAA1
                 ========================================
     "I press toward the mark for the prize of the high 
      calling of God in Christ Jesus."         
                                   Philippians 3:14 





view thread (8+ messages)  latest in thread

Message-ID: <199910231359.OAA30607@linda.lfix.co.uk>
Permalink:  ../199910231359.OAA30607@linda.lfix.co.uk/
Also on:    postgresql.org/message-id/199910231359.OAA30607@linda.lfix.co.uk

 · 

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: olly@lfix.co.uk, phd2@earthling.net, areiner@tph.tuwien.ac.at, olly@linda.lfix.co.uk
  Subject: Re: [SQL] Can VACUUM, but cannot do VACUUM ANALYZE
  In-Reply-To: <199910231359.OAA30607@linda.lfix.co.uk>
  References: <Pine.LNX.4.20.9910231202050.9896-100000@fep132.fep.ru> <199910231359.OAA30607@linda.lfix.co.uk>

* 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