Re: Timestamp conversion can't use index

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: thomas(at)pgsql(dot)com, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Timestamp conversion can't use index
Date: 2001-12-27 04:45:45
Message-ID: 200112270445.fBR4jjt05093@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


OK, new text:

Some datatype() function calls now evaluated differently

At least it is a warning.

---------------------------------------------------------------------------

> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> > Added to same files:
> > datatype(const,...) function calls now evaluated earlier
>
> This is quite wrong, since (a) the change only applies to single-
> argument function calls (so, no "..."), (b) the call is not
> evaluated "earlier", but "differently", and (c) it doesn't only
> apply to constant arguments.
>
> Not sure that I can come up with a one-liner definition of this change,
> but the above definitely doesn't do the job.
>
> We already have
>
> Modify type coersion logic to attempt binary-compatible functions first (Tom)
>
> and I'm not sure there is a better one-liner for it.
>
> regards, tom lane
>

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2001-12-27 05:00:02 Re: History question
Previous Message Tom Lane 2001-12-27 04:39:15 Re: Timestamp conversion can't use index