Re: proposal: plpgsql - Assert statement - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: proposal: plpgsql - Assert statement
Date
Msg-id 546CA4DF.9090502@dunslane.net
Whole thread Raw
In response to Re: proposal: plpgsql - Assert statement  (Simon Riggs <simon@2ndQuadrant.com>)
Responses Re: proposal: plpgsql - Assert statement  (Mike Blackwell <mike.blackwell@rrd.com>)
Re: proposal: plpgsql - Assert statement  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 11/19/2014 06:35 AM, Simon Riggs wrote:
> On 18 November 2014 21:19, Petr Jelinek <petr@2ndquadrant.com> wrote:
>
>> Personally, I see this as natural extension of the conditional block control
>> which we already have for loops with CONTINUE WHEN and EXIT WHEN. This
>> basically extends it to any block and it seems quite natural to have it for
>> me...
> That's a reasonable argument to include it.
>
> I seem to share the same opinion with Andrew: its not going to hurt to
> include this, but its not gonna cause dancing in the streets either. I
> would characterize that as 2 very neutral and unimpressed people, plus
> 3 in favour. Which seems enough to commit.
>
> Perhaps I misunderstand, Andrew?
>


That's about right, although I would put it a bit stronger than that. 
But if we're the only people unimpressed I'm not going to object further.

cheers

andrew



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Add shutdown_at_recovery_target option to recovery.conf
Next
From: Robert Haas
Date:
Subject: Re: [GENERAL] Performance issue with libpq prepared queries on 9.3 and 9.4