| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Caleb Welton <cwelton(at)greenplum(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [PATCH] bugfix for int2vectorin |
| Date: | 2009-12-02 03:52:32 |
| Message-ID: | 603c8f070912011952m33f67a7dm29a62944fc275396@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Dec 1, 2009 at 10:38 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Caleb Welton <cwelton(at)greenplum(dot)com> writes:
>> I believe the int2vectorin function should handle invalid input more cleanly.
>
> Why bother? Under what circumstances would users (or anyone at all)
> be putting data into an int2vector? It's an internal type and is
> certainly not meant for use in user tables.
Maybe it's just me, but this seems like an unnecessarily dismissive
response to a report of some rather odd-looking behavior.
...Robert
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua Tolley | 2009-12-02 03:53:49 | Re: PL/Python array support |
| Previous Message | Caleb Welton | 2009-12-02 03:52:29 | Re: [PATCH] bugfix for int2vectorin |