| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Jaime Casanova <jaime(at)2ndquadrant(dot)com>, Oleg Bartunov <oleg(at)sai(dot)msu(dot)su>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: NULL's support in SP-GiST |
| Date: | 2012-03-07 21:59:37 |
| Message-ID: | CA+TgmoaYgftYTDog6fy-5af1WFDeycDt5nw=h=q+L7khYj3r=Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Mar 7, 2012 at 4:03 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
>> I guess the question is whether this is a stop-ship item for spgist.
>> If it is, then we're going to have to spend the time to fix this, but
>> if not, then since it was submitted more than two weeks after the
>> start of the CommitFest, it seems we should postpone it to 9.3.
>
> If we buy into the assumption that nulls support can/should be bolted on
> after the fact, then postponing it to 9.3 would be reasonable. I wasn't
> very happy with that idea though, and would like to look at this issue
> before 9.2 gets frozen. So please don't pull it from the CF yet.
OK.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2012-03-07 21:59:46 | Re: Fix PL/Python metadata when there is no result |
| Previous Message | Robert Haas | 2012-03-07 21:57:12 | Re: psql COPY vs. ON_ERROR_ROLLBACK, multi-command strings |