Re: [HACKERS] Cached plans and statement generalization - Mailing list pgsql-hackers

From Konstantin Knizhnik
Subject Re: [HACKERS] Cached plans and statement generalization
Date
Msg-id 6ea1db86-b300-b57c-0f9d-a55dd3966175@postgrespro.ru
Whole thread Raw
In response to RE: [HACKERS] Cached plans and statement generalization  ("Nagaura, Ryohei" <nagaura.ryohei@jp.fujitsu.com>)
Responses RE: [HACKERS] Cached plans and statement generalization  ("Nagaura, Ryohei" <nagaura.ryohei@jp.fujitsu.com>)
RE: [HACKERS] Cached plans and statement generalization  ("Yamaji, Ryo" <yamaji.ryo@jp.fujitsu.com>)
List pgsql-hackers

On 29.01.2019 4:38, Nagaura, Ryohei wrote:
> Hi,
>
> Although I became your reviewer, it seems to be difficult to feedback in this CF.
> I continue to review, so would you update your patch please?
> Until then I review your current patch.
>
> There is one question.
> date_1.out which maybe is copy of date.out includes trailing space and gaps of indent
> e.g., line 3368 and 3380 in your current patch have
>     space in each end of line
>     different indent.
> This is also seen in date.out.
> I'm not sure whether it is ok to add new file including the above features just because a existing file includes.
> Is it ok?
>
> Best regards,
> ---------------------
> Ryohei Nagaura
Rebased version of the patch is attached.
Concerning spaces in date.out and date_1.out - it is ok.
This files are just output of test execution and it is not possible to 
expect lack of trailing spaces in output of test scripts execution.



-- 
Konstantin Knizhnik
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company


Attachment

pgsql-hackers by date:

Previous
From: Amit Langote
Date:
Subject: Re: speeding up planning with partitions
Next
From: Amit Kapila
Date:
Subject: Re: WIP: Avoid creation of the free space map for small tables