I just stumbled on the fact that the "assert_failure" exception seems to be
unhandleable. My test is at the end.
Is this intended?
I looked at the section:
«
43.9.2. Checking Assertions
https://www.postgresql.org/docs/current/plpgsql-errors-and-messages.html#PLPGSQL-STATEMENTS-ASSERT
»
It says
On Sunday, May 8, 2022, Bryn Llewellyn wrote:
>
> «
> Note that ASSERT is meant for detecting program bugs, not for reporting
> ordinary error conditions. Use the RAISE statement, described above,
> for that.
> »
>
> But it takes quite a stretch of the imagination to infer that this means
> that
> david.g.johns...@gmail.com wrote:
>
> I do understand better now and indeed the current limitation has no
> workaround that I can come up with. I was hoping maybe subblocks would work
> but its pretty clear cut that to catch an error at the commit command you
> must catch it within a block an
> david.g.johns...@gmail.com wrote:
>
>> b...@yugabyte.com wrote:
>>
>> «
>> Note that ASSERT is meant for detecting program bugs, not for reporting
>> ordinary error conditions. Use the RAISE statement, described above, for
>> that.
>> »
>>
>> But it takes quite a stretch of the imagination t
On Sat, 2022-05-07 at 12:06 +0200, Guillaume Lelarge wrote:
> Le sam. 7 mai 2022 à 10:21, Ron a écrit :
> > On 5/6/22 21:35, Hasan Marzooq wrote:
> > > I've some questions around Backup & Restore.
> > >
> > > 1: Is it necessary to perform a VACUUM and REINDEXING operation after
> > > restoring
