Re: [HACKERS] [sqlsmith] ERROR: badly formatted node string "RESTRICTINFO...
От | Amit Kapila |
---|---|
Тема | Re: [HACKERS] [sqlsmith] ERROR: badly formatted node string "RESTRICTINFO... |
Дата | |
Msg-id | CAA4eK1+dnAMZGKuWF8zEDtP7ZJf2G0kYgtHQgskkNM=D+7shsA@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: [HACKERS] [sqlsmith] ERROR: badly formatted node string "RESTRICTINFO... (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: [HACKERS] [sqlsmith] ERROR: badly formatted node string "RESTRICTINFO...
Re: [HACKERS] [sqlsmith] ERROR: badly formatted node string "RESTRICTINFO... |
Список | pgsql-hackers |
On Wed, Apr 12, 2017 at 12:40 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote: > Amit Kapila <amit.kapila16@gmail.com> writes: > >> However, the worker will >> never execute such a plan as we don't generate a plan where unsafe >> sublan/initplan is referenced in the node passed to the worker. If we >> want to avoid passing parallel-unsafe subplans to workers, then I >> think we can maintain a list of parallel safe subplans along with >> subplans in PlannerGlobal and PlannedStmt or maybe keep a parallel >> safe flag in Plan so that we can pass only parallel safe plans to >> workers. > > Right, we could, say, leave a hole in the subplan list corresponding > to any subplan that's not parallel-safe. That seems like a good idea > anyway because right now there's clearly no cross-check preventing > a worker from trying to run such a subplan. > > Anyone want to draft a patch for this? > Please find patch attached based on above discussion. -- With Regards, Amit Kapila. EnterpriseDB: http://www.enterprisedb.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
Вложения
В списке pgsql-hackers по дате отправления: