Re: CAST(... ON DEFAULT) - WIP build on top of Error-Safe User Functions - Mailing list pgsql-hackers

From Corey Huinker
Subject Re: CAST(... ON DEFAULT) - WIP build on top of Error-Safe User Functions
Date
Msg-id CADkLM=eidRg5VnDEPTK1y6QU1PB8QuzOB3xrsm0_X7DO2s984A@mail.gmail.com
Whole thread Raw
In response to Re: CAST(... ON DEFAULT) - WIP build on top of Error-Safe User Functions  (jian he <jian.universality@gmail.com>)
List pgsql-hackers
> The same logic applies to RangeVarGetRelidExtendedSafe() and
> makeRangeVarFromNameListSafe. These can be called from
> RangeVarGetRelidExtended() and makeRangeVarFromNameList(),
> respectively.
> --
>

I don’t see any way to pass the escontext (ErrorSaveContext) without changing
the textToQualifiedNameList function signature.
...
Am I missing something?

I think we need to keep these separate. The execution paths that don't care about capturing errors shouldn't be slowed down by minority of paths that do. That may change in the future, but if it does, we'll be getting rid of a lot of internal functions with this type of difference.

pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: meson and check-tests
Next
From: Andrew Dunstan
Date:
Subject: Re: [PATCH] Allow complex data for GUC extra.