| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
| Cc: | Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: access/parallel.h lacks PGDLLIMPORT |
| Date: | 2017-12-19 15:24:21 |
| Message-ID: | CA+TgmoZDnSXR4hwniFC2dJTGSTU8v0Gm3477JBP8v-BnQkNiuw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Dec 19, 2017 at 3:36 AM, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> wrote:
> I also think it is good to allow ParallelWorkerNumber to be used in
> extensions. Attached is the patch for same. I think for other two we
> should wait till there is really a good use case for them.
I think waiting for a "really good" use case is too high a bar. I
think we only need to think that there is a "reasonable" use case.
Accordingly, I pushed a commit adding PGDLLIMPORT to both
ParallelWorkerNumber and InitializingParallelWorker.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2017-12-19 15:31:04 | Re: [HACKERS] parallel.c oblivion of worker-startup failures |
| Previous Message | David Steele | 2017-12-19 15:15:25 | Re: MemoryContextCreate change in PG 11 how should contexts be created |