SELECT DISTINCT is picky about constants

From: Andreas Pflug <Andreas(dot)Pflug(at)web(dot)de>
To: pgsql-performance(at)postgresql(dot)org
Subject: SELECT DISTINCT is picky about constants
Date: 2003-02-04 12:15:46
Message-ID: 3E3FAEF2.5080302@web.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

The query
SELECT DISTINCT keycol, 'constant' FROM myTable
or
SELECT DISTINCT keycol, NULL FROM myTable

will result in an error message (7.3.1)

Unable to identify an ordering operator '<' for type "unknown"
Use explicit ordering operator or modify query

If I use 'constant'::varchar or NULL::varchar everything's fine.
Unfortunately, this SELECT DISTINCT will appear quite often in my app.

I'd rather like PostgreSQL to use implicit type casting for such
constants. The final type chosen doesn't matter anyway and life would be
easier.

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Rod Taylor 2003-02-04 14:29:13 Re: SELECT DISTINCT is picky about constants
Previous Message Bruce Momjian 2003-02-03 00:41:00 Re: Postgres 7.3.1 poor insert/update/search performance