| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: strange CREATE INDEX tab completion cases |
| Date: | 2016-01-11 13:09:12 |
| Message-ID: | CAB7nPqQAt2B0x7Uk0F1cFDOgw5S9nZ71t_PSAd-vWJA4B6dv7w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Jan 11, 2016 at 2:16 AM, Peter Eisentraut <peter_e(at)gmx(dot)net> wrote:
> On 12/13/15 9:16 AM, Michael Paquier wrote:
>> Please see the attached to address those things (and others) with
>> extra fixes for a couple of comments.
>
> I have ported these changes to the new world order and divided them up
> into more logical changes that are more clearly documented. Please
> check that this matches what you had in mind.
Thanks for the new patches, this fell of my radar. This new version
looks fine to me.
+ /* If we have CREATE|UNIQUE INDEX CONCURRENTLY, then add "ON"
and existing
+ indexes */
This comment format is not correct.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2016-01-11 13:11:18 | Re: Need help on pgcrypto |
| Previous Message | Vladimir Sitnikov | 2016-01-11 13:05:37 | Re: Re: 9.4-1207 behaves differently with server side prepared statements compared to 9.2-1102 |