When you retrieve it you'll get 13:22:48-0700 which is the same time as 20:22:48Z. Timestamptz will store 13:22:48-0700 as 20:22:48, the absolute point in time, but also remember that it was entered with 7 hours offset. timestamp with time zone also records the time zone it was entered in.įor example, 20:22:48Z and 13:22:48-0700 both represent the same moment in time, but the first is in Universal Coordinated Time and the other is 7 hours offset (Pacific Daylight Time). I'll refer to the timestamp types by their short names: timestamp without time zone is timestamp and timestamp with time zone is timestamptz.īoth timestamp and timestamptz store an absolute point in time. Which are really independent on the client session's timezone? How can I create a column with default timestamp values is there any way to get a timestamp independent of the client session's timezone? What am I missing? Could anyone explain in some details please.Īnd also. And I expected to get two values which are a few seconds apart, and not 4 hours apart. I always thought that in such scenario the clock_timestamp() call is executed on the server, and the timezone of the client session should not matter. I run the two inserts just a few seconds apart from each other.īut I get two very different values in the DB e.g. insert into public.test123(id) values (2) insert into public.test123(id) values (1) Ģ) In the second session I have timezone America/New_York and I do this. So from this session I do an insert as follows. The first session is from PG Admin, the second one is from DBeaver.ġ) In the first session when I run show timezone it returns UTC. I then insert into it from 2 different client sessions, (id int not null primary key, dt timestamp null default clock_timestamp())
0 kommentar(er)
