Re: [GENERAL] Concurrency problem building indexes
От | Jim C. Nasby |
---|---|
Тема | Re: [GENERAL] Concurrency problem building indexes |
Дата | |
Msg-id | 20060425001906.GO64695@pervasive.com обсуждение исходный текст |
Ответ на | Re: [GENERAL] Concurrency problem building indexes (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: [GENERAL] Concurrency problem building indexes
|
Список | pgsql-hackers |
On Mon, Apr 24, 2006 at 08:14:33PM -0400, Tom Lane wrote: > "Jim C. Nasby" <jnasby@pervasive.com> writes: > > Since this seems to only be an issue due to trying to update pg_class > > for the table, perhaps CREATE INDEX can just ignore errors there? > > Lessee, where would ignoring an error potentially cause the greatest > damage? I can hardly think of a less critical catalog than pg_class :-( Sorry, should have been more specific... as I understand it, the update is just to set pg_class.relpages for the heap, which shouldn't be critical. Was the code ever changed so that it won't update relpages if the number is the same? -- Jim C. Nasby, Sr. Engineering Consultant jnasby@pervasive.com Pervasive Software http://pervasive.com work: 512-231-6117 vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
В списке pgsql-hackers по дате отправления: