Horton

Re: support fast default for domain with constraints

Viktor Holmberg <v@viktorh.net>

View thread View on postgr.es
From: Viktor Holmberg <v@viktorh.net>
To: Andrew Dunstan <andrew@dunslane.net>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2026-03-13T10:17:43Z
Lists: pgsql-hackers 
Ok, understand. No worries at all, just thought I’d flag it up.

/Viktor
On 13 Mar 2026 at 11:13 +0100, Andrew Dunstan <andrew@dunslane.net>, wrote:
>
> On 2026-03-13 Fr 4:43 AM, Viktor Holmberg wrote:
> > Nice that this was pushed. On a minor note, I saw that my email got confused in the commit (viktor.holmberg@aiven.io) instead of v@viktorh.net. (I don’t know what aiven.io is). I don’t know if there is a way to change this without messing up the git log? If not it’s no problem, probably unlikely that anyone will contact me about it anyways.
>
> It's not really possible. My deepest apologies. Some how or other the gadget I have for ensuring I credit everyone I should got confused. I will disable it until I can figure out where it went wrong.
>
> cheers
>
> andrew
>
> --
> Andrew Dunstan
> EDB: https://www.enterprisedb.com

Commits

  1. Enable fast default for domains with non-volatile constraints

  2. Extend DomainHasConstraints() to optionally check constraint volatility

  3. Restrict virtual columns to use built-in functions and types

  4. Replace EEOP_DONE with special steps for return/no return

  5. Add soft error handling to some expression nodes