Postgres Pro
Downloads
Home   >   mailing lists

Re: [HACKERS] PoC plpgsql - possibility to force custom or genericplan - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: [HACKERS] PoC plpgsql - possibility to force custom or genericplan
Date
Msg-id cf3a7077-c350-2bb0-24b7-431d58af8e06@2ndquadrant.com
Whole thread Raw
In response to Re: [HACKERS] PoC plpgsql - possibility to force custom or generic plan  (Simon Riggs <simon@2ndquadrant.com>)
Responses Re: [HACKERS] PoC plpgsql - possibility to force custom or generic plan
List pgsql-hackers
Tree view 
On 9/8/17 13:14, Simon Riggs wrote:
> 2. Allow a SET to apply only for a single statement
> SET guc1 = x, guc2 = y FOR stmt
> e.g. SET max_parallel_workers = 4 FOR SELECT count(*) FROM bigtable
> Internally a GUC setting already exists for a single use, via
> GUC_ACTION_SAVE, so we just need to invoke it.

This doesn't read well to me.  It indicates to me "make this setting for
this query [in case I run it later]", but it does not indicate that the
query will be run.

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services


-- 
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 by date:

Previous
From: Pavel Stehule
Date:
Subject: Re: [HACKERS] Re: proposal - using names as primary names of plpgsqlfunction parameters instead $ based names
Next
From: Tom Lane
Date:
Subject: Re: [HACKERS] PoC plpgsql - possibility to force custom or generic plan