From: | Joshua Reich <josh(at)root(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Proposed patch for contrib/cube |
Date: | 2006-07-17 20:33:26 |
Message-ID: | 44BBF416.8050907@root.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom: Thanks for the out-of-band posting to the documentation. I think
the new version (attached) addresses your issues.
What is the general process for submitting patches? Is there a URL
someone can point me towards to learn more?
Thanks,
Josh Reich
Tom Lane wrote:
> Joshua Reich <josh(at)root(dot)net> writes:
>> ... build a cube by specifying 2 arrays, one for the UR
>> coordinate, one for LL.
>> I hope people find this useful, and if so, we can add it to contrib/cube.
>
> Seems useful, but it needs work: it will fail on toasted arrays or
> arrays containing nulls. I'd suggest converting it to V1 call protocol
> too, as the V1 GETARG macros are the easiest answer to the toasting
> problem. Null array elements are a new issue in CVS HEAD, you'd need
> to test against HEAD for that.
>
> As a matter of style, would it be better to error out if the arrays
> are not the same length?
>
> regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Have you searched our list archives?
>
> http://archives.postgresql.org
Attachment | Content-Type | Size |
---|---|---|
cube_from_arrays.c | text/plain | 1.4 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Tino Wildenhain | 2006-07-17 20:54:46 | Re: plpython sets |
Previous Message | Steve Atkins | 2006-07-17 20:26:03 | Re: automatic system info tool? |