Re: Exclusion constraint issue

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: David Fetter <david(at)fetter(dot)org>
Cc: Eric McKeeth <eldin00(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: Exclusion constraint issue
Date: 2010-09-26 14:15:00
Message-ID: 29345.1285510500@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

David Fetter <david(at)fetter(dot)org> writes:
> On Fri, Sep 24, 2010 at 05:22:15PM -0400, Tom Lane wrote:
>> period() might be immutable, but those casts from date to
>> timestamptz are not, because they depend on the TimeZone parameter.

> How hard would it be to point out the first expression found to be
> mutable?

I looked at that yesterday. It would take significant restructuring
of the code involved :-( ... the place that throws the error doesn't
know exactly what subnode was found to be mutable, and IIRC it hasn't
got access to the original command string anyway.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message David Fetter 2010-09-26 15:41:28 Re: Exclusion constraint issue
Previous Message Tom Lane 2010-09-26 14:07:23 Re: 9.0RC1 error variable not found in subplantarget lists