| From: | Cédric Villemain <cedric(dot)villemain(dot)debian(at)gmail(dot)com> |
|---|---|
| To: | Jens Wilke <jens(dot)wilke(at)affinitas(dot)de> |
| Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: undead index |
| Date: | 2011-05-06 09:12:52 |
| Message-ID: | BANLkTi=OG8Mkft01drRF6ONWSE5QzbYA+w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
2011/5/6 Jens Wilke <jens(dot)wilke(at)affinitas(dot)de>:
> On Thursday 05 May 2011 16:46:05 Cédric Villemain wrote:
>
>> I understood that you droped an index and when you dump/restore you
>> get your index again.
>
> Yes, that's it, after the pg_upgrade error, i removed the target data
> directory, and initialzed a new target DB.
> After pg_dumpall|pg_dump i got an index that is not visible in the source DB.
> It had either been deleted weeks ago or disappeared from the system catalog
> for any other reason.
> I can't find this index in a new pg_dumpall output from the source DB.
Okay! (I didn't understood correctly), please check the question from Tom.
--
Cédric Villemain 2ndQuadrant
http://2ndQuadrant.fr/ PostgreSQL : Expertise, Formation et Support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vincent De Groote | 2011-05-06 09:36:14 | Foreign key in composite values |
| Previous Message | Jens Wilke | 2011-05-06 07:49:46 | Re: undead index |