Re: pg_upgrade problem with invalid indexes
| От | Bruce Momjian | 
|---|---|
| Тема | Re: pg_upgrade problem with invalid indexes | 
| Дата | |
| Msg-id | 20121207011636.GP30893@momjian.us обсуждение исходный текст | 
| Ответ на | Re: pg_upgrade problem with invalid indexes (Tom Lane <tgl@sss.pgh.pa.us>) | 
| Ответы | Re: pg_upgrade problem with invalid indexes | 
| Список | pgsql-hackers | 
On Thu, Dec 6, 2012 at 07:53:57PM -0500, Tom Lane wrote: > Bruce Momjian <bruce@momjian.us> writes: > > Yes, I thought of not dumping it. The problem is that we don't delete > > the index when it fails, so I assumed we didn't want to lose the index > > creation information. I need to understand why we did that. > > Because CREATE INDEX CONCURRENTLY can't drop the index if it's already > failed. It's not because we want to do that, it's an implementation > restriction of the horrid kluge that is CREATE/DROP INDEX CONCURRENTLY. Well, what is the logic that pg_dump dumps it then, even in non-binary-upgrade mode? -- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + It's impossible for everything to be true. +
В списке pgsql-hackers по дате отправления: