Received: from sss2.sss.pgh.pa.us (sss.pgh.pa.us [209.114.166.2]) by hub.org (8.9.3/8.9.3) with ESMTP id LAA75583 for ; Fri, 26 May 2000 11:53:00 -0400 (EDT) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss2.sss.pgh.pa.us (8.9.3/8.9.3) with ESMTP id LAA02215; Fri, 26 May 2000 11:52:57 -0400 (EDT) To: "Mitch Vincent" cc: pgsql-sql@postgresql.org Subject: Re: date() indexing error.. In-reply-to: <00a601bfc71f$05ed13c0$4100000a@venux.net> References: <00a601bfc71f$05ed13c0$4100000a@venux.net> Comments: In-reply-to "Mitch Vincent" message dated "Fri, 26 May 2000 10:31:04 -0400" Date: Fri, 26 May 2000 11:52:57 -0400 Message-ID: <2212.959356377@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200005/160 "Mitch Vincent" writes: > Using PostgreSQL 7.0 I'm Doing ... > ipa2=# CREATE INDEX "app_stat_month" on applicant_stats(date(month)); > ERROR: SQL-language function not supported in this context. > ipa2=# \d applicant_stats > Table "applicant_stats" > Attribute | Type | Modifier > -----------+-----------+---------- > app_id | integer | > month | date | > user_id | integer | > view_time | timestamp | > Index: app_id Since month is already a 'date', applying date() to it is pretty pointless. I don't really know why we have date(date) defined at all, but we do, and it's defined as an SQL-language function --- which indexes don't support at the moment. Thus the error message. There are a fair number of no-op functions in pg_proc that are defined as SQL "SELECT $1". We could probably afford to lose 'em all, and let the parser treat these things as implicit type conversions instead... regards, tom lane