Re: feature request ctid cast / sql exception

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
Cc: Vladimír Houba ml(dot) <v(dot)houba(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: feature request ctid cast / sql exception
Date: 2021-04-17 19:46:37
Message-ID: 356033.1618688797@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"David G. Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> writes:
> On Sat, Apr 17, 2021 at 10:58 AM Vladimír Houba ml. <v(dot)houba(at)gmail(dot)com>
> wrote:
>> Another nice feature would be a function that can be called from a sql
>> statement and would throw an exception when executed.

> An assertion-related extension in core would be welcomed.

This has been suggested before, but as soon as you start looking
at the details you find that it's really hard to get a one-size-fits-all
definition that's any simpler than the existing plpgsql RAISE
functionality. Different people have different ideas about how
much decoration they want around the message. So, if 10% of the
world agrees with your choices and the other 90% keeps on using
a custom plpgsql function to do it their way, you haven't really
improved matters much. OTOH a 90% solution might be interesting to
incorporate in core, but nobody's demonstrated that one exists.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Vladimír Houba ml. 2021-04-17 19:58:08 Re: feature request ctid cast / sql exception
Previous Message Mark Dilger 2021-04-17 19:43:21 Re: pg_amcheck option to install extension