Re: BUG #15350: Getting invalid cache ID: 11 Errors
От | Tom Lane |
---|---|
Тема | Re: BUG #15350: Getting invalid cache ID: 11 Errors |
Дата | |
Msg-id | 20462.1535424017@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: BUG #15350: Getting invalid cache ID: 11 Errors (Thomas Munro <thomas.munro@enterprisedb.com>) |
Ответы |
Re: BUG #15350: Getting invalid cache ID: 11 Errors
Re: BUG #15350: Getting invalid cache ID: 11 Errors Re: BUG #15350: Getting invalid cache ID: 11 Errors |
Список | pgsql-bugs |
Thomas Munro <thomas.munro@enterprisedb.com> writes: > We could probably improve that situation by making syscache lookups > (and probably other things too) fail when called from _PG_init() in > regular backends so that extension authors are made aware of this > hazard, or perhaps go the other way and change the order we do things > in parallel workers. Hmm. There's an argument to be made for the latter: we don't really want stuff failing in parallel workers if it works fine normally. On the other hand, it seems clear to me that we *don't* want extensions to be doing stuff like syscache lookups in _PG_init(), because that would prevent them from working as shared_preload_libraries entries. And on the third hand, intentionally breaking code that used to work isn't likely to win us many friends either. So I'm not sure that your first option is really tenable. Perhaps we could get away with doing it in HEAD and not back-patching ... but that does little for existing problems. regards, tom lane
В списке pgsql-bugs по дате отправления: