| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [COMMITTERS] pgsql: Mark JSON error detail messages for translation. |
| Date: | 2012-06-13 14:35:31 |
| Message-ID: | 9778.1339598131@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Tue, Jun 12, 2012 at 9:52 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> The code for this is as attached. Note that I'd rip out the normal-path
>> tracking of line boundaries; it seems better to have a second scan of
>> the data in the error case and save the cycles in non-error cases.
> Really?!
Um ... do you have a problem with that idea, and if so what? It would
be considerably more complicated to do it without a second pass.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2012-06-13 15:03:38 | Re: [COMMITTERS] pgsql: Mark JSON error detail messages for translation. |
| Previous Message | Peter Eisentraut | 2012-06-13 10:42:49 | pgsql: Improve documentation of postgres -C option |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2012-06-13 14:40:32 | Re: [PATCH 16/16] current version of the design document |
| Previous Message | Merlin Moncure | 2012-06-13 14:21:12 | Re: [PATCH 16/16] current version of the design document |