Re: Bad cast priority for DATE? - Mailing list pgsql-hackers

From Josh Berkus
Subject Re: Bad cast priority for DATE?
Date
Msg-id 4C940F47.50801@agliodbs.com
Whole thread Raw
In response to Re: Bad cast priority for DATE?  (Tom Lane <tgl@sss.pgh.pa.us>)
List 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
 


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: VACUUM produces odd freespace values
Next
From: Thom Brown
Date:
Subject: Re: VACUUM produces odd freespace values