| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Greg Stark <stark(at)mit(dot)edu> |
| Cc: | Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PG Hackers <pgsql-hackers(at)postgresql(dot)org>, Stephen Frost <sfrost(at)snowman(dot)net>, Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>, David Fetter <david(at)fetter(dot)org>, Josh Berkus <josh(at)agliodbs(dot)com> |
| Subject: | Re: Review: UNNEST (and other functions) WITH ORDINALITY |
| Date: | 2013-08-13 19:20:43 |
| Message-ID: | CA+TgmobWg86k+VZT7+znZ-dVoxT8mt4xBGUiEvVeCbbzC3LGPw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Aug 6, 2013 at 6:10 PM, Greg Stark <stark(at)mit(dot)edu> wrote:
> The only other case I could come up with in my regression tests is pretty
> esoteric:
>
> CREATE COLLATION nulls (locale='C');
> ALTER OPERATOR CLASS text_ops USING btree RENAME TO first;
> CREATE TABLE nulls_first(t text);
> CREATE INDEX nulls_first_i ON nulls_first(t COLLATE nulls first);
>
> I'm not 100% sure there aren't other cases where this can occur though.
Blech. Well, that's why we need to stop hacking the lexer before we shoot
a hole through our foot that's too large to ignore. But it's not this
patch's job to fix that problem.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Fetter | 2013-08-13 19:57:14 | Re: How to create read-only view on 9.3 |
| Previous Message | Merlin Moncure | 2013-08-13 18:53:40 | Re: How to create read-only view on 9.3 |