> -Original Message-
> From: Matthew
>
> > > The vacuum I tried in single user mode failed (froze on a
> > > table, for over 20 minutes) so I killed it.
> >
> > Did you destroy indices before vacuum?
> >
> Not all of them, it's a large database and I am trying to get it up
> and runni
> What do you mean by the whole database? I have already
> executed:
>
> reindex database cms force
> reindex table cases force
> reindex table cases force
> reindex table hits force
> reindex table history force (and a few more)
>
> How do I get it do
> The vacuum I tried in single user mode failed (froze on a
> table, for over 20 minutes) so I killed it.
Did you destroy indices before vacuum?
Vadim
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
> > The vacuum I tried in single user mode failed (froze on a
> > table, for over 20 minutes) so I killed it.
>
> Did you destroy indices before vacuum?
>
Not all of them, it's a large database and I am trying to get it up
and running asap.
FYI now when I try to use psql to conn
> Matthew <[EMAIL PROTECTED]> writes:
> > FYI now when I try to use psql to connect to the database I get this
> > error:
> > bash$ psql cms
> > psql: FATAL 1: cannot find attribute 1 of relation pg_trigger
>
> So the indexes on pg_attribute are hosed too. I wonder whether that was
Matthew <[EMAIL PROTECTED]> writes:
> What do you mean by the whole database? I have already executed:
> reindex database cms force
(checks manual...) That appears to be the right syntax. If you did
that in a standalone backend with the appropriate command line options
(-O and -P)
> > > The vacuum I tried in single user mode failed (froze on a
> > > table, for over 20 minutes) so I killed it.
> >
> > Did you destroy indices before vacuum?
> >
> Not all of them, it's a large database and I am trying
> to get it up and running asap.
Did you destroy *all* indices of table
Matthew <[EMAIL PROTECTED]> writes:
> FYI now when I try to use psql to connect to the database I get this
> error:
> bash$ psql cms
> psql: FATAL 1: cannot find attribute 1 of relation pg_trigger
So the indexes on pg_attribute are hosed too. I wonder whether that was
the orig
> Postgre 7.0.3, on RedHat Linux 6.2 stock 2.2.16 kernel. Nothing special I
> can think of, this server has been up and in use for the last 128 days
> with
> no problem. Last night while cron was performing the nightly vacuuming of
> all databases on one of our servers, I got this from cron.
>
> Matthew <[EMAIL PROTECTED]> writes:
> > [ a tale of woe ]
>
> It looks like dropping and rebuilding *all* the indexes on your history
> table would be a good move (possibly with a vacuum of the table while
> the indexes are removed). You might want to do a COPY out to try to
> save the table d
Matthew <[EMAIL PROTECTED]> writes:
> [ a tale of woe ]
It looks like dropping and rebuilding *all* the indexes on your history
table would be a good move (possibly with a vacuum of the table while
the indexes are removed). You might want to do a COPY out to try to
save the table data before the
> I have since stopped the database server and all my users are
> dead in the water at the moment. I took postgres down to single
> user mode and I'm doing a vacuum and was considering doing an
> iccpclean. Any other suggestions? dump & restore?
> Any Idea what happened?
Drop indices; vacuum; c
Postgre 7.0.3, on RedHat Linux 6.2 stock 2.2.16 kernel. Nothing special I
can think of, this server has been up and in use for the last 128 days with
no problem. Last night while cron was performing the nightly vacuuming of
all databases on one of our servers, I got this from cron.
Vacuuming cm
13 matches
Mail list logo
