From: | frant101(at)googlemail(dot)com |
---|---|
To: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: Reindex + relation doesnt exist |
Date: | 2008-03-11 16:36:53 |
Message-ID: | a3829100-62e8-4633-8154-97f5dbba7784@h25g2000hsf.googlegroups.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On Mar 11, 3:07 pm, t(dot)(dot)(dot)(at)sss(dot)pgh(dot)pa(dot)us (Tom Lane) wrote:
> frant(dot)(dot)(dot)(at)googlemail(dot)com writes:
> > I have tried to put the schema name in front of the index name put i
> > still get the same error.
> > ./reindexdb -e --index sc1.ind1 hermes
> > reindexdb: reindexing of index "sc1.ind1" in database "hermes" failed:
> > ERROR: relation "sc1.ind1" does not exist
>
> AFAICS reindexdb won't allow that --- it quotes the name you supply,
> so that's going to look like a table name that happens to contain a
> dot, not a schema and table name.
>
> You didn't say where you are inserting the non-default schema path
> into your interactive sessions...
>
> regards, tom lane
>
> --
> Sent via pgsql-admin mailing list (pgsql-ad(dot)(dot)(dot)(at)postgresql(dot)org)
> To make changes to your subscription:http://www.postgresql.org/mailpref/pgsql-admin
I guess what i will need to do is put the following command in the
script :
SET search_path TO sc1;
and then use the standard REINDEX command and this should do the job
for me...
Just that i need to run the job out of hours as i cant afford the
table to be locked through work hours and the index seems to have
swelled to 3GB even though the table is only 1GB
thanks again for the help
Fran
From | Date | Subject | |
---|---|---|---|
Next Message | sathiya psql | 2008-03-12 05:27:27 | migration of 7.4 to 8.1 |
Previous Message | Alvaro Herrera | 2008-03-11 15:21:24 | Re: FILL FACTOR information |