| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
| Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: bug in json_to_record with arrays |
| Date: | 2014-12-02 00:27:20 |
| Message-ID: | 10371.1417480040@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Merlin Moncure <mmoncure(at)gmail(dot)com> writes:
> On Mon, Dec 1, 2014 at 3:01 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> I'd be good with going to "invalid input syntax" if we also change
>> record_in to match. Anyone have a feeling pro or con about that?
> I don't know. "malformed array literal" is a mighty big clue that you
> have a bad "postgres format" array literal and will be well supported
> by googling -- this problem isn't new.
Good point about googling, and after all we are already using "malformed
array literal" for a subset of these cases. Let's stick with that
wording.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2014-12-02 00:33:15 | Re: excessive amounts of consumed memory (RSS), triggering OOM killer |
| Previous Message | Tomas Vondra | 2014-12-02 00:26:00 | Re: excessive amounts of consumed memory (RSS), triggering OOM killer |