| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | "Shulgin, Oleksandr" <oleksandr(dot)shulgin(at)zalando(dot)de>, Ryan Pedela <rpedela(at)datalanche(dot)com> |
| Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, hlinnaka <hlinnaka(at)iki(dot)fi>, Merlin Moncure <mmoncure(at)gmail(dot)com>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com> |
| Subject: | Re: [PATCH] Generalized JSON output functions |
| Date: | 2015-07-17 14:11:40 |
| Message-ID: | 55A90D1C.2040000@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 07/17/2015 08:20 AM, Shulgin, Oleksandr wrote:
> > This patch makes Postgres core more complex
>
> Yes, it does. But, that was not the purpose, obviously. :-)
>
> > while not really solving the problem in Javascript.
>
> It still allows for less risk of silent data corruption on the js side.
>
>
I have already pointed out how this patch is fundamentally broken. You
can achieve your aims by a fairly small amount of code inside your
logical decoder, and with no core code changes whatsoever. So I'm
puzzled why we are even still debating this broken design.
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2015-07-17 14:16:21 | Re: pgsql: Retain comments on indexes and constraints at ALTER TABLE ... TY |
| Previous Message | Fabien | 2015-07-17 13:50:06 | pgbench stats per script & other stuff |