On 23/12/2016 13:41, Peter J. Holzer wrote:
> On 2016-12-09 16:52:05 +0800, Qiu Xiafei wrote:
>> I'm new to PG and want to implement my domain-specific system based on PG. I
>> wish to arrange my data as several tables in database and translate my DSL
>> into
>> SQL statements for query. Since one
On 08/07/2019 16:23, Andrew Gierth wrote:
>>>>>> "Tom" == Tom Mercha writes:
>
> Tom> Hi All
>
> Tom> As we know, a query goes through number of stages before it is
> Tom> executed. One of these stages is query optimization (QO).
>
On 08/07/2019 18:29, Tom Lane wrote:
> Andrew Gierth writes:
>> "Tom" == Tom Lane writes:
>> Tom> Two I'd particularly draw your attention to are
>> Tom> join_collapse_limit and from_collapse_limit --- if you set both to
>> Tom> 1, that'll effectively disable searching for a good join order
On 08/07/2019 02:04, Rob Sargent wrote:
>
>
>> On Jul 7, 2019, at 6:02 PM, Rob Sargent wrote:
>>
>>
>>
>>> On Jul 7, 2019, at 6:01 PM, Rob Sargent >> <mailto:robjsarg...@gmail.com>> wrote:
>>>
>>>
>>>
>
On 08/07/2019 01:46, Rob Sargent wrote:
>
>
>> On Jul 7, 2019, at 5:22 PM, Tom Mercha wrote:
>>
>> Hi All
>>
>> As we know, a query goes through number of stages before it is executed.
>> One of these stages is query optimization (QO).
>>
>
Hi All
As we know, a query goes through number of stages before it is executed.
One of these stages is query optimization (QO).
There are various parameters to try and influence optimizer decisions
and costs. But I wanted to measure the effect of such a stage by turning
it off completely and I
