Re: [HACKERS] Parallel worker error - Mailing list pgsql-hackers

From Pavan Deolasee
Subject Re: [HACKERS] Parallel worker error
Date
Msg-id CABOikdPOMSxy1vSizvT7m2i2eQ1J2+gZ2DMR_sSe=8svCp9u4A@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] Parallel worker error  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers

On Wed, Aug 30, 2017 at 8:49 PM, Robert Haas <robertmhaas@gmail.com> wrote:


But since that's an established design fl^H^Hprinciple, maybe that
means we should go with the approach of teaching SerializeGUCState()
to ignore role altogether and instead have ParallelWorkerMain call
SetCurrentRoleId using information passed via the FixedParallelState
(not sure of the precise details here).


Seems like a reasonable approach to me. 

Thanks,
Pavan

--
 Pavan Deolasee                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services

pgsql-hackers by date:

Previous
From: Dilip Kumar
Date:
Subject: Re: [HACKERS] Proposal: Improve bitmap costing for lossy pages
Next
From: Tatsuro Yamada
Date:
Subject: Re: [HACKERS] CLUSTER command progress monitor