Does vacuumdb read pg_autovacuum ?
If not, can I specify multiple comma-separated tables to pass as
arguments to vacuumdb ? The list of tables that need to be vacuumed
is a constant and hence easier to manage the vacuuming process.
On Fri, Oct 30, 2009 at 3:04 PM, Alvaro Herrera
wrote:
> Anj Ad
Alvaro,
Why don't you just create a sql script with a separate vacuum command for each
table you need to vacuum?
-Original Message-
From: pgsql-admin-ow...@postgresql.org on behalf of Anj Adu
Sent: Sun 11/1/2009 8:03 AM
To: Alvaro Herrera
Cc: pgsql-admin@postgresql.org
Subject: Re: [ADM
My goal is to reset the XID wraparound counter by performing vacuumdb
(autovacuum is not an option for my for various reasons)
On Sun, Nov 1, 2009 at 8:06 AM, Igor Polishchuk wrote:
> Alvaro,
> Why don't you just create a sql script with a separate vacuum command for
> each table you need to va
Hi all;
I have a client with a table which has an exeedingly large amount of bloat, so
we plan to rebuild the table. However in setting up a test box I've found
that both the PK and another UNIQUE index column have duplicate values.
In theory the INDEX/PK should refuse to build if dupes exist
Anj Adu escribió:
> Does vacuumdb read pg_autovacuum ?
>
> If not, can I specify multiple comma-separated tables to pass as
> arguments to vacuumdb ? The list of tables that need to be vacuumed
> is a constant and hence easier to manage the vacuuming process.
No, but you can write a simple scrip
Anj Adu escribió:
> My goal is to reset the XID wraparound counter by performing vacuumdb
> (autovacuum is not an option for my for various reasons)
Note that if you are on 8.1 (I can't recall) you need to vacuum the
whole database in a single command for Xid wraparound. Only on 8.2 and
higher yo
Kevin Kempter writes:
> Anyone have any Idea how this could happen?
Corrupt indexes. What PG version are we talking about?
regards, tom lane
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.or
Kevin Kempter writes:
> On Sunday 01 November 2009 15:50:20 you wrote:
>> Kevin Kempter writes:
>>> Anyone have any Idea how this could happen?
>>
>> Corrupt indexes. What PG version are we talking about?
> version 8.3.8
Well, there aren't any known causes of btree index corruption in 8.3.x,
On Sunday 01 November 2009 16:25:58 Tom Lane wrote:
> Kevin Kempter writes:
> > On Sunday 01 November 2009 15:50:20 you wrote:
> >> Kevin Kempter writes:
> >>> Anyone have any Idea how this could happen?
> >>
> >> Corrupt indexes. What PG version are we talking about?
> >
> > version 8.3.8
>
>
