From: | Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk> |
---|---|
To: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
Cc: | Atri Sharma <atri(dot)jiit(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: WIP Patch for GROUPING SETS phase 1 |
Date: | 2014-08-21 07:37:42 |
Message-ID: | 87r40aqph5.fsf@news-spur.riddles.org.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
>>>>> "Heikki" == Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> writes:
> On 08/13/2014 09:43 PM, Atri Sharma wrote:
>> Sorry, forgot to attach the patch for fixing cube in contrib,
>> which breaks since we now reserve "cube" keyword. Please find
>> attached the same.
Heikki> Ugh, that will make everyone using the cube extension
Heikki> unhappy. After this patch, they will have to quote contrib's
Heikki> cube type and functions every time.
Heikki> I think we should bite the bullet and rename the extension,
I agree, the contrib/cube patch as posted is purely so we could test
everything without having to argue over the new name first. (And it
is posted separately from the main patch because of its length and
utter boringness.)
However, even if/when a new name is chosen, there's the question of
how to make the upgrade path easiest. Once CUBE is reserved,
up-to-date pg_dump will quote all uses of the "cube" type and function
when dumping an older database (except inside function bodies of
course), so there may be merit in keeping a "cube" domain over the new
type, and maybe also merit in keeping the extension name.
So what's the new type name going to be? cuboid? hypercube?
geometric_cube? n_dimensional_box?
--
Andrew (irc:RhodiumToad)
From | Date | Subject | |
---|---|---|---|
Next Message | Heikki Linnakangas | 2014-08-21 07:42:14 | Re: [TODO] Process pg_hba.conf keywords as case-insensitive |
Previous Message | Michael Paquier | 2014-08-21 07:20:11 | Re: Specifying the unit in storage parameter |