From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com> |
Cc: | Rich Shepard <rshepard(at)appl-ecosys(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Yet Another Timestamp Question: Time Defaults |
Date: | 2013-01-21 19:27:34 |
Message-ID: | 9154.1358796454@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com> writes:
> On 01/21/2013 07:26 AM, Rich Shepard wrote:
>> What is the behavior if a column data type is timestamptz but there is
>> only the date portion available? There must be a default time; can that be
>> defined?
> Easy enough to test:
> test=# create table ts_test(ts_fld timestamp with time zone);
> CREATE TABLE
> test=# insert into ts_test VALUES ('2013-01-21');
> INSERT 0 1
> test=# SELECT * from ts_test ;
> ts_fld
> ------------------------
> 2013-01-21 00:00:00-08
Note that that default is local midnight according to your current
timezone setting (from which we may guess that Adrian lives on the US
west coast, or somewhere in that general longitude).
> Not sure you can change the default supplied by Postgres,
"SET timezone" ought to do it ...
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Rich Shepard | 2013-01-21 19:37:17 | Re: Yet Another Timestamp Question: Time Defaults |
Previous Message | Edson Richter | 2013-01-21 19:25:45 | Re: What is impact of "varchar_opts"? |