From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Didier Gasser-Morlay" <didiergm(at)gmail(dot)com> |
Cc: | pgsql-novice(at)postgresql(dot)org |
Subject: | Re: index with no column |
Date: | 2008-04-26 20:07:47 |
Message-ID: | 21204.1209240467@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
"Didier Gasser-Morlay" <didiergm(at)gmail(dot)com> writes:
> I have setup an automated backup/restore between two machines, all is
> fine. Bar on thing: after restoring mu database, I had a message about
> several errors ignored (I did not keep a log of these errors), but I
> am seing on several tables, some indexes declared but pgadmin3 fails
> to show any columns. I had to manually drop the indexes and recreate
> them
This is really not enough information to guess what was wrong.
But I'm thinking what you saw was at least partly a pgadmin bug.
Postgres doesn't support zero-column indexes, so if pgadmin showed
them as being such, it was mistaken.
If you want to investigate more closely, please reproduce the problem
from scratch, and this time keep a log of what errors you got and what
statements they were in response to. Then compare what pgadmin
and psql \d have to say about it.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Adam Šindelář | 2008-04-28 19:22:11 | difference between 'where' and 'having' |
Previous Message | Didier Gasser-Morlay | 2008-04-26 18:51:34 | index with no column |