Re: BUG #15309: ERROR: catalog is missing 1 attribute(s) for relid760676 when max_parallel_maintenance_workers > 0
От | Peter Geoghegan |
---|---|
Тема | Re: BUG #15309: ERROR: catalog is missing 1 attribute(s) for relid760676 when max_parallel_maintenance_workers > 0 |
Дата | |
Msg-id | CAH2-WzkkS6Dis3fGeSCZsDXv41tCT5pB_QwSzmV-DXMVrmpoow@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: BUG #15309: ERROR: catalog is missing 1 attribute(s) for relid 760676 when max_parallel_maintenance_workers > 0 (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: BUG #15309: ERROR: catalog is missing 1 attribute(s) for relid 760676 when max_parallel_maintenance_workers > 0
|
Список | pgsql-bugs |
On Mon, Aug 6, 2018 at 2:29 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote: > Hm. Post-beta3, I think I'd vote for a conservative fix in v11, > which seems to be "ban for mapped catalogs". Feel free to make > it work in HEAD, though. Makes sense. I'm not sure if it's worth pursuing parallel mapped catalog index builds much further, though. I doubt that ordinary users care about whether or not this is supported, so this is a matter of principle. I don't feel strongly on whether or not I should make mapped builds work on HEAD, so I defer to you, and anyone else that might have an interest. Does it matter, do you think? It might be worth teaching heap_beginscan_parallel() to cross-check each worker's heap relation's rd_smgr.smgr_node to a version of the same field from the leader, stored in shared memory (in the ParallelHeapScanDesc). That way, any future recurrence of a similar bug will be far easier to detect. A "can't happen" error along these lines seems like it would be worthwhile. -- Peter Geoghegan
В списке pgsql-bugs по дате отправления: