Re: jsonb_set() strictness considered harmful to data

From: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
To: Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com>
Cc: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Floris Van Nee <florisvannee(at)optiver(dot)com>, Ariadne Conill <ariadne(at)dereferenced(dot)org>, Mark Felder <feld(at)freebsd(dot)org>, "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: jsonb_set() strictness considered harmful to data
Date: 2019-10-21 15:06:46
Message-ID: f66263f4-7dce-610a-5dbe-060375a8d840@aklaver.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

On 10/20/19 11:07 PM, Tomas Vondra wrote:
> On Sun, Oct 20, 2019 at 06:51:05PM -0400, Andrew Dunstan wrote:

>
> True. And AFAIK catching exceptions is not really possible in some code,
> e.g. in stored procedures (because we can't do subtransactions, so no
> exception blocks).
>

Can you explain the above to me as I thought there are exception blocks
in stored functions and now sub-transactions in stored procedures.

--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Avinash Kumar 2019-10-21 15:10:22 Re: Postgres Point in time Recovery (PITR),
Previous Message Thomas Kellerer 2019-10-21 14:45:27 Re: Calling jsonb_array_elements 4 times in the same query

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2019-10-21 15:07:28 intermittent test failure on Windows
Previous Message Andrew Dunstan 2019-10-21 13:28:06 Re: jsonb_set() strictness considered harmful to data