Re: [HACKERS] PoC plpgsql - possibility to force custom or generic plan

On 12.07.18 11:12, Pavel Stehule wrote: > This appears to be the patch of record in this thread.  I think there is > general desire for adding a setting like this, and the implementation is > simple enough. > > One change perhaps: How about naming the default setting "auto" instead

Re: [HACKERS] PoC plpgsql - possibility to force custom or generic plan

On 2018/07/12 18:12, Pavel Stehule wrote: Hi 2018-07-10 12:01 GMT+02:00 Peter Eisentraut mailto:peter.eisentr...@2ndquadrant.com>>: On 23.01.18 17:08, Pavel Stehule wrote: > attached updated patch This appears to be the patch of record in this thread.  I think there is general

Re: [HACKERS] PoC plpgsql - possibility to force custom or generic plan

Hi 2018-07-10 12:01 GMT+02:00 Peter Eisentraut < peter.eisentr...@2ndquadrant.com>: > On 23.01.18 17:08, Pavel Stehule wrote: > > attached updated patch > > This appears to be the patch of record in this thread. I think there is > general desire for adding a setting like this, and the implementa

Re: [HACKERS] PoC plpgsql - possibility to force custom or generic plan

On 23.01.18 17:08, Pavel Stehule wrote: > attached updated patch This appears to be the patch of record in this thread. I think there is general desire for adding a setting like this, and the implementation is simple enough. One change perhaps: How about naming the default setting "auto" instead

Re: [HACKERS] PoC plpgsql - possibility to force custom or generic plan

2018-03-02 3:43 GMT+01:00 Pavel Stehule : > > > 2018-03-02 3:38 GMT+01:00 Andres Freund : > >> On 2018-03-02 03:13:04 +0100, Pavel Stehule wrote: >> > 2018-03-01 23:10 GMT+01:00 Andres Freund : >> > >> > > On 2018-01-23 17:08:56 +0100, Pavel Stehule wrote: >> > > > 2018-01-22 23:15 GMT+01:00 Steph

Re: [HACKERS] PoC plpgsql - possibility to force custom or generic plan

2018-03-02 3:38 GMT+01:00 Andres Freund : > On 2018-03-02 03:13:04 +0100, Pavel Stehule wrote: > > 2018-03-01 23:10 GMT+01:00 Andres Freund : > > > > > On 2018-01-23 17:08:56 +0100, Pavel Stehule wrote: > > > > 2018-01-22 23:15 GMT+01:00 Stephen Frost : > > > > > This really could use a new thread

Re: [HACKERS] PoC plpgsql - possibility to force custom or generic plan

On 2018-03-02 03:13:04 +0100, Pavel Stehule wrote: > 2018-03-01 23:10 GMT+01:00 Andres Freund : > > > On 2018-01-23 17:08:56 +0100, Pavel Stehule wrote: > > > 2018-01-22 23:15 GMT+01:00 Stephen Frost : > > > > This really could use a new thread, imv. This thread is a year old and > > > > about a

Re: [HACKERS] PoC plpgsql - possibility to force custom or generic plan

2018-03-01 23:10 GMT+01:00 Andres Freund : > On 2018-01-23 17:08:56 +0100, Pavel Stehule wrote: > > 2018-01-22 23:15 GMT+01:00 Stephen Frost : > > > This really could use a new thread, imv. This thread is a year old and > > > about a completely different feature than what you've implemented here.

Re: [HACKERS] PoC plpgsql - possibility to force custom or generic plan

On 2018-01-23 17:08:56 +0100, Pavel Stehule wrote: > 2018-01-22 23:15 GMT+01:00 Stephen Frost : > > This really could use a new thread, imv. This thread is a year old and > > about a completely different feature than what you've implemented here. > > > > true, but now it is too late At the very

Re: [HACKERS] PoC plpgsql - possibility to force custom or generic plan

2018-01-30 9:06 GMT+01:00 Tatsuro Yamada : > On 2018/01/24 1:08, Pavel Stehule wrote: > >> >> >> 2018-01-22 23:15 GMT+01:00 Stephen Frost > sfr...@snowman.net>>: >> >> Pavel, >> >> >> * Pavel Stehule (pavel.steh...@gmail.com > pavel.steh...@gmail.com>) wrote: >> > here is a GUC based p

Re: [HACKERS] PoC plpgsql - possibility to force custom or generic plan

On 2018/01/24 1:08, Pavel Stehule wrote: 2018-01-22 23:15 GMT+01:00 Stephen Frost mailto:sfr...@snowman.net>>: Pavel, * Pavel Stehule (pavel.steh...@gmail.com ) wrote: > here is a GUC based patch for plancache controlling. Looks so this code is

Re: [HACKERS] PoC plpgsql - possibility to force custom or generic plan

2018-01-22 23:15 GMT+01:00 Stephen Frost : > Pavel, > > * Pavel Stehule (pavel.steh...@gmail.com) wrote: > > here is a GUC based patch for plancache controlling. Looks so this code > is > > working. > > This really could use a new thread, imv. This thread is a year old and > about a completely di

Re: [HACKERS] PoC plpgsql - possibility to force custom or generic plan

2018-01-23 15:35 GMT+01:00 Robert Haas : > On Mon, Jan 22, 2018 at 5:15 PM, Stephen Frost wrote: > > Pavel, > > > > * Pavel Stehule (pavel.steh...@gmail.com) wrote: > >> here is a GUC based patch for plancache controlling. Looks so this code > is > >> working. > > > > This really could use a new

Re: [HACKERS] PoC plpgsql - possibility to force custom or generic plan

On Mon, Jan 22, 2018 at 5:15 PM, Stephen Frost wrote: > Pavel, > > * Pavel Stehule (pavel.steh...@gmail.com) wrote: >> here is a GUC based patch for plancache controlling. Looks so this code is >> working. > > This really could use a new thread, imv. This thread is a year old and > about a comple

Re: [HACKERS] PoC plpgsql - possibility to force custom or generic plan

Pavel, * Pavel Stehule (pavel.steh...@gmail.com) wrote: > here is a GUC based patch for plancache controlling. Looks so this code is > working. This really could use a new thread, imv. This thread is a year old and about a completely different feature than what you've implemented here. > It is

Re: [HACKERS] PoC plpgsql - possibility to force custom or generic plan

On Thu, Oct 12, 2017 at 6:31 PM, Pavel Stehule wrote: > It is hard to create regress tests. Any ideas? Moving to next CF per lack of reviews. -- Michael