"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
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
In response to
pgsql-novice by date
|Next:||From: Adam Šindelář||Date: 2008-04-28 19:22:11|
|Subject: difference between 'where' and 'having'|
|Previous:||From: Didier Gasser-Morlay||Date: 2008-04-26 18:51:34|
|Subject: index with no column|