Postgres Pro
Downloads
Home   >   mailing lists

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

From Tatsuro Yamada
Subject Re: [HACKERS] PoC plpgsql - possibility to force custom or genericplan
Date
Msg-id 83191da0-afe8-03fd-f496-c2c08e072612@lab.ntt.co.jp
Whole thread Raw
In response to Re: [HACKERS] PoC plpgsql - possibility to force custom or generic plan  (Pavel Stehule <pavel.stehule@gmail.com>)
List pgsql-hackers
Tree view 
On 2018/07/12 18:12, Pavel Stehule wrote:
> Hi
> 
> 2018-07-10 12:01 GMT+02:00 Peter Eisentraut <peter.eisentraut@2ndquadrant.com
<mailto:peter.eisentraut@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 implementation is
>     simple enough.
> 
>     One change perhaps: How about naming the default setting "auto" instead
>     of "default".  That makes it clearer what it does.
> 
> 
> I changed "default" to "auto"
> 
> updated patch attached
> 
> Regards
> 
> Pavel

Hi Pavel,

I tested your patch on 40ca70eb.
Here is the result.

=======================
  All 190 tests passed.
=======================

Thanks,
Tatsuro Yamada

pgsql-hackers by date:

Previous
From: Thomas Munro
Date:
Subject: Re: ON CONFLICT DO NOTHING on pg_dump
Next
From: Heikki Linnakangas
Date:
Subject: Re: [HACKERS] Re: [COMMITTERS] pgsql: Remove pgbench "progress" testpending solution of its timing is (fwd)