Re: [HACKERS] Refactoring identifier checks to consistently use strcmp - Mailing list pgsql-hackers

From Daniel Gustafsson
Subject Re: [HACKERS] Refactoring identifier checks to consistently use strcmp
Date
Msg-id 62991614-9673-4276-99CC-6754E7A0572F@yesql.se
Whole thread Raw
In response to Re: [HACKERS] Refactoring identifier checks to consistently usestrcmp  (Michael Paquier <michael.paquier@gmail.com>)
Responses Re: [HACKERS] Refactoring identifier checks to consistently usestrcmp
List pgsql-hackers
> On 24 Jan 2018, at 02:37, Michael Paquier <michael.paquier@gmail.com> wrote:
> On Tue, Jan 23, 2018 at 04:22:22PM +0100, Daniel Gustafsson wrote:
>> On 23 Jan 2018, at 05:52, Michael Paquier <michael.paquier@gmail.com> wrote:

>>> Those are changed as well in the attached, which applies on top of your
>>> v6. I have added as well in it the tests I spotted were missing. If this
>>> looks right to you, I am fine to switch this patch as ready for
>>> committer, without considering the issues with isCachable and isStrict
>>> in CREATE FUNCTION of course.
>>
>> Apart from the amproperty hunk, I’m definately +1 on adding your patch on top
>> of my v6 one.  Thanks for all your help and review!
>
> OK. Could you publish a v7? I will switch the entry as ready for
> committer.

Attached is a rebased v7 patch which has your amendments (minus propname) which
passes make check without errors.

The volatility patch is also rebased included, but there the discussion whether
to keep or drop the deprecated syntax first needs to happen (started in your
20180115022748.GB1724@paquier.xyz mail).

cheers ./daniel


Attachment

pgsql-hackers by date:

Previous
From: Amit Langote
Date:
Subject: Re: non-bulk inserts and tuple routing
Next
From: KAWAMICHI Ryoji
Date:
Subject: Re: proposal: alternative psql commands quit and exit