Re: CREATE CAST allows creation of binary-coercible cast to range over domain

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Richard Guo <guofenglinux(at)gmail(dot)com>
Cc: Peter Eisentraut <peter(at)eisentraut(dot)org>, pgsql-bugs <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: CREATE CAST allows creation of binary-coercible cast to range over domain
Date: 2024-08-21 14:09:58
Message-ID: 1773683.1724249398@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Richard Guo <guofenglinux(at)gmail(dot)com> writes:
> I wonder if it would be better for readability to list these types in
> the order we check them in the code, as we did previously, i.e.:

The previous order seemed quite random to me, because enums aren't
container types and the reason for excluding them isn't really the
same. I thought about re-ordering the code to match the new comment,
but desisted. We could do that though...

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Marcin Barczyński 2024-08-21 14:49:43 Re: REINDEX INDEX pg_catalog.pg_default_acl_role_nsp_obj_index stuck waiting for transaction from the future in PG 13.16
Previous Message Rémi Cura 2024-08-21 13:30:08 Re: BUG #18587: PLPGSQL : conflict between variable and ON CONFLICT (a_column)