From: | "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com> |
---|---|
To: | "LARC/J(dot)L(dot)Shipman/jshipman" <Jeffery(dot)L(dot)Shipman(at)nasa(dot)gov> |
Cc: | PostgreSQL <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: reindexing |
Date: | 2008-02-24 23:32:03 |
Message-ID: | dcc563d10802241532w5a0b0824j695d74b765654b17@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Fri, Feb 22, 2008 at 12:24 PM, LARC/J.L.Shipman/jshipman
<Jeffery(dot)L(dot)Shipman(at)nasa(dot)gov> wrote:
> Hi,
> I am reindexing my 7.1.4 postgres database. The postmaster seems to
> create processes for each reindex request. Is there any way to find
> out more about the processes.
>
> ps -aef | grep postgres
>
> yields the following, but does not tell me which table is being
> reindexed or anything meaningful
> about the process.
My pgsql-fu regarding obsolete versions is obsolete. You do realize
that 7.1.x hasn't been supported for a very long time, and for very
good reasons, right? It's not just obsolete in terms of being
outdated by more modern versions, but is known to have a few data
eating bugs, not to mention the txid wraparound issue. You should be
planning on how to upgrade it first, then things like this might be
less necessary and / or less of a problem to work with.
In later versions of pgsql you've got a stats collector that can do
things like tell you what queries are running. As well as
autovacuuming and non-full vacuums that make things like reindexing
mostly uneeded.
From | Date | Subject | |
---|---|---|---|
Next Message | Erik Jones | 2008-02-25 00:08:01 | Re: "RETURNS SETOF" function question |
Previous Message | Dean Gibson (DB Administrator) | 2008-02-24 22:42:10 | Re: v7.4 pg_dump(all) need to encode from SQL_ASCII to UTF8 |