Re: Assignment of valid collation for SET operations on queries with UNKNOWN types.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Ashutosh Bapat <ashutosh(dot)bapat(at)enterprisedb(dot)com>
Cc: Rahila Syed <rahilasyed90(at)gmail(dot)com>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Assignment of valid collation for SET operations on queries with UNKNOWN types.
Date: 2017-01-23 13:19:18
Message-ID: 16103.1485177558@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Ashutosh Bapat <ashutosh(dot)bapat(at)enterprisedb(dot)com> writes:
> Following error message might be misleading,

> postgres=# create table t1 (a unknown);
> ERROR: column "a" has pseudo-type unknown

> UNKNOWN is not exactly a pseudo-type.

Well, as I said to Michael just now, I think we should turn it into one
now that we're disallowing it in tables, because "cannot be used as a
table column" is more or less the definition of a pseudotype. In any
case, the average user probably thinks UNKNOWN is a pseudotype, if they
think about it at all. So I think this message is fine even if we left
it as-is.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tomas Vondra 2017-01-23 13:27:39 Re: Checksums by default?
Previous Message Tom Lane 2017-01-23 13:14:52 Re: Assignment of valid collation for SET operations on queries with UNKNOWN types.