| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Parallel worker error |
| Date: | 2017-08-31 19:11:10 |
| Message-ID: | CA+TgmoZ8GXS2MTXY-TZCLs2pYZMPRuSuWMiejYZDHikFcPJVqQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Aug 30, 2017 at 11:19 AM, Robert Haas <robertmhaas(at)gmail(dot)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).
Could I get some opinions on the virtues of this approach, vs. any of
the other suggestions at or near
http://postgr.es/m/CA+TgmoaSP90E33-MU2YpGs73TtJ37m5Hv-xqHjc7TPqX9wX8ew@mail.gmail.com
?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2017-08-31 19:38:33 | Re: expanding inheritance in partition bound order |
| Previous Message | Robert Haas | 2017-08-31 19:08:37 | Re: Assorted leaks and weirdness in parallel execution |