From: Steve Wampler <swampler@noao.edu>
To: Neil Conway <neilc@samurai.com>
Cc: Postgres-performance <pgsql-performance@postgresql.org>
Subject: Re: Help tracking down problem with inserts slowing
Date: Sun, 07 Dec 2003 10:28:50 -0700
Message-ID: <1070818130.20063.145.camel@weaver.tuc.noao.edu> (raw)
In-Reply-To: <87fzfy96ns.fsf@mailbox.samurai.com>
References: <1070661108.20063.86.camel@weaver.tuc.noao.edu>
<87fzfy96ns.fsf@mailbox.samurai.com>
On Fri, 2003-12-05 at 16:38, Neil Conway wrote:
>
> (1) Can you confirm that the VACUUM FULL on site B actually
> removed all the tuples you intended it to remove? Concurrent
> transactions can limit the amount of data that VACUUM FULL is
> able to reclaim. If you run contrib/pgstattuple (or compare
> the database's disk consumption with the number of live rows
> in it), you should be able to tell.
Hmmm, I installed 7.2.3 from RPMs, but the contrib package seems
to be missing the pgstattuple library code. (According to the
readme, I should do:
$ make
$ make install
$ psql -e -f /usr/local/pgsql/share/contrib/pgstattuple.sql test
but the first two lines don't make sense with the binary rpm
distribution and trying the last line as (for my world):
->psql -e -f /usr/share/pgsql/contrib/pgstattuple.sql
farm.devel.configdb
yields:
DROP FUNCTION pgstattuple(NAME);
psql:/usr/share/pgsql/contrib/pgstattuple.sql:1: ERROR:
RemoveFunction: function 'pgstattuple(name)' does not exist
CREATE FUNCTION pgstattuple(NAME) RETURNS FLOAT8
AS '$libdir/pgstattuple', 'pgstattuple'
LANGUAGE 'c' WITH (isstrict);
psql:/usr/share/pgsql/contrib/pgstattuple.sql:4: ERROR: stat failed
on file '$libdir/pgstattuple': No such file or directory
I don't need this right now (a reindex seems to have fixed
our problem for now...), but it sounds like it would be useful
in the future.
Thanks!
Steve
--
Steve Wampler -- swampler@noao.edu
The gods that smiled on your birth are now laughing out loud.
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-performance@postgresql.org
Cc: swampler@noao.edu, neilc@samurai.com
Subject: Re: Help tracking down problem with inserts slowing
In-Reply-To: <1070818130.20063.145.camel@weaver.tuc.noao.edu>
References: <1070661108.20063.86.camel@weaver.tuc.noao.edu> <87fzfy96ns.fsf@mailbox.samurai.com> <1070818130.20063.145.camel@weaver.tuc.noao.edu>
* 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