Check your postgresql.conf on both, see if you set the default timezone in either. Also, reconsider seriously whether timestamp without timezone is the correct type for your use here. > On Jun 23, 2017, at 12:37 AM, Om Prakash Jaiswal <op12om@xxxxxxxxxxx> wrote: > > > At RHEL6.5 32bit OS, PostgreSQL 9.0.4(Attached File IMG_20170623_093733_HDR.jpg) > EPOCH value is different for the same time and data type > > from > At RHEL7.3 64bit OS, PostgreSQL 9.4.8.(Attached File IMG_20170623_094034_HDR.jpg > > > EPOCH value At RHEL7.3 64bit OS, PostgreSQL 9.4.8. and At RHEL7.3 64bit OS, PostgreSQL 9.6.3 are same. > > At everywhere I have select 'Asia/Kolkata' time zone in both OS and postgresql.conf file. > > Kindly look the matter and resolve the issue. > I am using in a Big project. Now I want to update postgreSQL version. I am getting this problem. > Because of that our client application is displaying actual time + 5:30 Hours. > Now I need to change in client application code to display correct time. Which will increase more man power. > > Kindly resolve the issue. > > Regards > Om Prakash > DBA, Bangalore > Mob: 9035635787 > > > > <IMG_20170623_093733_HDR.jpg><IMG_20170623_094034_HDR.jpg> > -- > Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-admin -- Scott Ribe scott_ribe@xxxxxxxxxxxxxxxx (303) 722-0567 -- Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
