On 2018-02-21 11:41:31 -0800, Brian Cloutier wrote:
> On Wed, Feb 21, 2018 at 10:14 AM, Andres Freund wrote:
>
> > Could you take the relevant commit, backport it to the
> > relevant branches, resolve conflicts, make possibly appropriate
> > adaptions, and post?
> >
>
> The original commit touch
On Wed, Feb 21, 2018 at 10:14 AM, Andres Freund wrote:
> Could you take the relevant commit, backport it to the
> relevant branches, resolve conflicts, make possibly appropriate
> adaptions, and post?
>
The original commit touched some new variables and therefore didn't apply
cleanly. Attached a
Hi,
On 2018-02-16 12:57:40 -0800, Brian Cloutier wrote:
> Thanks for committing this! We forgot to ask though, could you please
> backport this patch to 10 and maybe even 9.6? As-is I don't think these
> variables will be available until PG 11.
I think these days our policy is to do that on reque
On Fri, Feb 9, 2018 at 1:01 PM, Robert Haas wrote:
>
> Committed.
Thanks for committing this! We forgot to ask though, could you please
backport this patch to 10 and maybe even 9.6? As-is I don't think these
variables will be available until PG 11.
On Wed, Feb 7, 2018 at 6:32 AM, Metin Doslu wrote:
> i. The list of Pascal (max_worker_processes was already with
> PGDLLIMPORT, so I also added to max_parallel_workers)
> ii. Some others in cost.h to make the file more readable.
Committed.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.c
Thank you Metin !
Regards
PAscal
--
Sent from: http://www.postgresql-archive.org/PostgreSQL-hackers-f1928748.html
Hey all,
I'm attaching the updated patch, it includes
i. The list of Pascal (max_worker_processes was already with
PGDLLIMPORT, so I also added to max_parallel_workers)
ii. Some others in cost.h to make the file more readable.
Best,
Metin
On Tue, Feb 6, 2018 at 10:40 PM, Peter Geoghegan wrote:
On Tue, Feb 6, 2018 at 12:39 PM, Robert Haas wrote:
> Yeah, let's get them all into one list and I'll commit the whole thing
> together.
+1
--
Peter Geoghegan
On Tue, Feb 6, 2018 at 3:34 PM, legrand legrand
wrote:
> Hello,
> I know an other extension that would need the same for:
>
> src/include/optimizer/paths.h
> geqo_threshold
> enable_geqo
> min_parallel_index_scan_size
> min_parallel_table_scan_size
>
> src/include/optimizer/cost.h
> max_parallel_w
Hello,
I know an other extension that would need the same for:
src/include/optimizer/paths.h
geqo_threshold
enable_geqo
min_parallel_index_scan_size
min_parallel_table_scan_size
src/include/optimizer/cost.h
max_parallel_workers_per_gather
enable_hashjoin
enable_mergejoin
enable_nestloop
enable_in
> I would like to add PGDLLIMPORT to enable_hashagg for the same reason. I'm
> adding a very simple patch. Please let me know if I'm missing anything given
> that this is my first patch submission.
Seems weird to do it just for enable_hashagg and not for all of the
surroundin
Hey all,
There was already a discussion and commit for adding PGDLLIMPORT to some
variables which enables extensions to use them on Windows builds. For
reference, the previous thread:"Add PGDLLIMPORT lines to some variables".
I would like to add PGDLLIMPORT to enable_hashagg for the s
12 matches
Mail list logo
