Re: BUG #15726: parallel queries failed ERROR: invalid name syntax CONTEXT: parallel worker
От | Tom Lane |
---|---|
Тема | Re: BUG #15726: parallel queries failed ERROR: invalid name syntax CONTEXT: parallel worker |
Дата | |
Msg-id | 29888.1554218381@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: BUG #15726: parallel queries failed ERROR: invalid name syntaxCONTEXT: parallel worker (Thomas Munro <thomas.munro@gmail.com>) |
Ответы |
Re: BUG #15726: parallel queries failed ERROR: invalid name syntaxCONTEXT: parallel worker
|
Список | pgsql-bugs |
Thomas Munro <thomas.munro@gmail.com> writes: > On Tue, Apr 2, 2019 at 10:59 PM ANASTACIO Tiago > <tiago_anastacio@yahoo.fr> wrote: >> A pity background worker are no more verbose (DEBUG5) than: >> 2019-04-02 09:42:38.993 GMT [17654] ERROR: invalid name syntax > I agree, it would be nice to improve that. It seems to be a general > problem with any GUC that requires a transaction to check: parallel > workers will force that, but you might not understand the error > because it comes with no context. That gives me an idea: perhaps we > should set the elog() context while restoring GUCs, so that it is > displayed in the error output somehow. Yeah, something like CONTEXT: while setting parameter guc_variable_name to "some value" would likely make this a whole lot more comprehensible. And I think it could probably be done in a fairly centralized way using an error callback. regards, tom lane
В списке pgsql-bugs по дате отправления: