pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Josh Berkus <josh@agliodbs.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: Timestamp operator error
Date: Mon, 25 Feb 2002 23:47:35 -0500
Message-ID: <27308.1014698855@sss.pgh.pa.us> (raw)
In-Reply-To: <web-810140@davinci.ethosmedia.com>
References: <web-810140@davinci.ethosmedia.com>

"Josh Berkus" <josh@agliodbs.com> writes:
> Any suggestions on an emergency fix for my (production) database?

Emergency fix?  This operator didn't behave reasonably in 7.1 either
(at least not by my definition of reasonable).  What exactly would
you have us do?

>> I suspect this is good ammunition for the argument I've made from
>> time to time that we have too many implicit conversions, not too few.

> Yes, definitely.  Frankly, I'd prefer a large reduction in implicit
>  conversions; I just got into trouble with the difference between
>  current_timestamp and current_date that I would have caught much
>  earlier if Postgres had disallowed the implicit conversion. 

Yah.  Offhand I'd argue that no information-discarding conversion
should be implicitly invokable.  date->timestamp is fine;
timestamp->date should require an explicit cast.  I've already proposed
that we add a flag to pg_proc to distinguish implicit from explicit
conversion operations, and no one complained.  But we have not yet
begun to argue about exactly which conversions should be allowed
implicitly...

			regards, tom lane



view thread (10+ messages)  latest in thread

Message-ID: <27308.1014698855@sss.pgh.pa.us>
Permalink:  ../27308.1014698855@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/27308.1014698855@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-sql@postgresql.org
  Cc: tgl@sss.pgh.pa.us, josh@agliodbs.com
  Subject: Re: Timestamp operator error
  In-Reply-To: <27308.1014698855@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox