Re: Bad cast priority for DATE?

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Bad cast priority for DATE?
Date: 2010-09-18 01:00:55
Message-ID: 4C940F47.50801@agliodbs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


> timestamptz is a preferred type, so no you probably can't change that
> without breaking a lot of stuff. It's not immediately clear to me why
> that's wrong anyway.

Just that having a value implicitly acquire time zone information it
didn't originally have seems dangerous. But I can't come up with a
specific example of breakage right now -- at least not one on a single
server.

--
-- Josh Berkus
PostgreSQL Experts Inc.
http://www.pgexperts.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Thom Brown 2010-09-18 01:15:26 Re: VACUUM produces odd freespace values
Previous Message Bruce Momjian 2010-09-18 01:00:48 Re: VACUUM produces odd freespace values