On 02/20/2014 04:59 AM, Dev Kumkar wrote:
On Thu, Feb 20, 2014 at 4:31 AM, Adrian Klaver <adrian.klaver@xxxxxxxxxxx <mailto:adrian.klaver@xxxxxxxxxxx>> wrote: It depends on how you are declaring the timestamp field. If you do not use with time zone then the input value is open to interpretation and is not 'anchored' to a point in time. Example My time zone is currently PST. test=> create table timestamp_test(id int, ts timestamp, ts_z timestamp with time zone); CREATE TABLE test=> insert into timestamp_test values (1, now(), now()); INSERT 0 1 ..... If you know what time zone the value was inserted under you can get it back. . . That assumes a lot, so the best thing is to use timestamp with time zone. Thanks for trying this out on your setup. However looks like my requirement is different here.
So what is your requirement? Do you have a specific application/use for the databases you are installing?
Regards...
-- Adrian Klaver adrian.klaver@xxxxxxxxxxx -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
