Re: pgsql/src/backend parser/parse_coerce.c utils/ ...

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Thomas Lockhart <lockhart(at)fourpalms(dot)org>
Cc: pgsql-committers(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org
Subject: Re: pgsql/src/backend parser/parse_coerce.c utils/ ...
Date: 2001-10-04 18:06:38
Message-ID: 29485.1002218798@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

Thomas Lockhart <lockhart(at)fourpalms(dot)org> writes:
>> Make the world safe for atttypmod=0 ... this didn't use to mean anything,
>> but timestamp now wants it to mean something.

> What was the effect of this?

coerce_type_typemod thought that typmod=0 meant it shouldn't perform any
length coercion. But typmod=0 is now a valid value for timestamp ...

regards, tom lane

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message tgl 2001-10-04 19:13:56 pgsql/src/backend/utils/fmgr dfmgr.c
Previous Message Thomas Lockhart 2001-10-04 17:57:59 Re: pgsql/src/backend parser/parse_coerce.c utils/ ...

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2001-10-04 18:13:29 Re: timestamp resolution?
Previous Message Tom Lane 2001-10-04 18:03:13 Unhappiness with forced precision conversion for timestamp