pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Richard Guo <guofenglinux@gmail.com>
Cc: Peter Eisentraut <peter@eisentraut.org>
Cc: pgsql-bugs <pgsql-bugs@postgresql.org>
Subject: Re: CREATE CAST allows creation of binary-coercible cast to range over domain
Date: Wed, 21 Aug 2024 10:09:58 -0400
Message-ID: <1773683.1724249398@sss.pgh.pa.us> (raw)
In-Reply-To: <CAMbWs4_NfUheqvfnjgM9DatOB9sO0==a5js=QUfF9Z_0OxhPLA@mail.gmail.com>
References: <076968e1-0852-40a9-bc0b-117cd3f0e43c@eisentraut.org>
	<1537781.1724165175@sss.pgh.pa.us>
	<1611527.1724175039@sss.pgh.pa.us>
	<2e7acd5f-5d34-4802-a5e2-fa36433d133c@eisentraut.org>
	<CAMbWs4_NfUheqvfnjgM9DatOB9sO0==a5js=QUfF9Z_0OxhPLA@mail.gmail.com>

Richard Guo <guofenglinux@gmail.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





view thread (6+ messages)

Message-ID: <1773683.1724249398@sss.pgh.pa.us>
Permalink:  ../1773683.1724249398@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/1773683.1724249398@sss.pgh.pa.us

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-bugs@postgresql.org
  Cc: tgl@sss.pgh.pa.us, guofenglinux@gmail.com, peter@eisentraut.org
  Subject: Re: CREATE CAST allows creation of binary-coercible cast to range over domain
  In-Reply-To: <1773683.1724249398@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox