pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Steven M. Wheeler <swheeler@sabre.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-sql@hub.org
Subject: Re: [SQL] Questions about vacuum analyze
Date: Fri, 01 Oct 1999 17:24:38 -0500
Message-ID: <37F534A6.520A8A37@sabre.com> (raw)
References: <20576.938814148@sss.pgh.pa.us>

Boy this is fun! ;-}

I have upgraded to 6.5.2 as you suggest. Binaries are built and I am now
re-running my vacuum just to give my self a benchmark starting point.

Just wanted to let you know that, for perl5, when I tried to run "make
test" after having built the perl kit, I get the following:

cobra:/opt/pgsql/postgresql-6.5.2/src/interfaces/perl5 $make test
PERL_DL_NONLAZY=1 /usr/bin/perl -Iblib/arch -Iblib/lib
-I/usr/lib/perl5/i386-linux -I/usr/lib/perl5 test.pl
Pg::conndefaults ........ ok
Pg::connectdb ........... ok
$conn->exec ............. ok
$conn->errorMessage ..... ok
pqReadData() -- backend closed the channel unexpectedly.
        This probably means the backend terminated abnormally
        before or while processing the request.
make: *** [test_dynamic] Error 255

Am I better off re-writing my perl scripts in 'C'?  I've been thinking
about it in hopes of boosting the performance.

--
Steven Wheeler
UNIX Engineering
(918) 292-4119


Tom Lane wrote:

> "Steven M. Wheeler" <swheeler@sabre.com> writes:
> > DB: version 6.5
> > 33 hours [to vacuum] - WOW!
>
> Yipes.  We did find and fix a glitch in memory allocation in vacuum
> (causing both slowness and excessive memory usage) between 6.5 and
> 6.5.2.  You might try updating to see if it's gotten any better...
>
>                         regards, tom lane




view thread (23+ messages)  latest in thread

Message-ID: <37F534A6.520A8A37@sabre.com>
Permalink:  ../37F534A6.520A8A37@sabre.com/
Also on:    postgresql.org/message-id/37F534A6.520A8A37@sabre.com

 · 

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 using the --to and --cc options:
  reply via email

  To: pgsql-sql@postgresql.org
  Cc: swheeler@sabre.com, tgl@sss.pgh.pa.us, pgsql-sql@hub.org
  Subject: Re: [SQL] Questions about vacuum analyze
  In-Reply-To: <37F534A6.520A8A37@sabre.com>

* 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