From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Devrim GÜNDÜZ <devrim(at)gunduz(dot)org>, Dave Page <dpage(at)pgadmin(dot)org>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Flex output missing from 9.1a4 tarballs? |
Date: | 2011-03-22 21:44:04 |
Message-ID: | 7525.1300830244@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Tue, Mar 15, 2011 at 10:00 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> FWIW, collations are probably still several days away from being
>> noticeably less broken than they were in alpha4.
> How much less broken are they now?
I think the core code is only locally broken now, with issues like LIKE
index optimization probably not doing the right thing. The main problem
at this point is probably plpgsql. To get far with that, we're going to
need to extend the parser's Param interfaces to allow specification of a
collation for a Param. And SPI too. (Yay, still another generation of
SPI interfaces that we'll have to support forever...)
So, another couple days minimum before it's reasonable to ship. At
least if you want stuff like this to work:
http://archives.postgresql.org/message-id/20110314194507.GC13507@huehner.biz
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Stark | 2011-03-22 21:44:06 | Re: pgsql: Throw error for indeterminate collation of an ORDER/GROUP/DISTIN |
Previous Message | Radosław Smogura | 2011-03-22 21:28:02 | Re: 2nd Level Buffer Cache |