| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Greg Stark <gsstark(at)mit(dot)edu> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: TIMESTAMP WITH( OUT)? TIME ZONE indexing/type choice... |
| Date: | 2003-02-19 06:34:26 |
| Message-ID: | 9000.1045636466@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Greg Stark <gsstark(at)mit(dot)edu> writes:
> I just don't see what use a timestamp that doesn't represent a particular time
> would ever be. It seems to serve only as a gotcha for unwary programmers who
> take the default.
I have a problem with that too :-( ... timestamptz seems much the more
generally useful type. But the SQL spec is pretty definite that
"timestamp" means "timestamp without time zone".
Is anybody interested in the idea of a GUC parameter to choose whether
"timestamp" means "timestamp with time zone" (useful) or "timestamp
without time zone" (anally spec-compliant)? Or would that just muddy
the waters even more than they are already? We already changed the
meaning once...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Colin Mangiagalli | 2003-02-19 07:09:30 | Re: Transaction Logs Recycling Problem |
| Previous Message | Peter Childs | 2003-02-19 06:04:58 | Re: 7.3.1 takes long time to vacuum table? |