Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dO0sL-0004i6-HI for pgsql-admin@arkaria.postgresql.org; Thu, 22 Jun 2017 12:06:18 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1dO0sK-0004qc-Fc for pgsql-admin@arkaria.postgresql.org; Thu, 22 Jun 2017 12:06:16 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1dO0sJ-0004q6-F4 for pgsql-admin@postgresql.org; Thu, 22 Jun 2017 12:06:15 +0000 Received: from sonic307-3.consmr.mail.sg3.yahoo.com ([106.10.241.180]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1dO0sC-0001ZI-E9 for pgsql-admin@postgresql.org; Thu, 22 Jun 2017 12:06:14 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.co.in; s=s2048; t=1498133163; bh=Vm4nmDvmNiNFl5bAekBXO5omqP+8NeUeSH89PMSBCmE=; h=Date:From:Reply-To:To:Subject:References:From:Subject; b=sPjAZDvw9EWMpMWxfO0hrQJCofGyWFX+QRk2C3Ui4QQSfCp019iNI6OMz4ncFnaJaMvERLfk2D+jKNmfcM2P1sBVzWMUnhVkBtvu2v5I5sPK8CdoAQL/nSGVLgXmM5+r3aBqz0/KNUScre8ne1czXiXEdD06XtXmhJqdkYPJo8ZgGRFWn+9n7bvLBMNjWaH4Ioh9XyeiGWbjCnf8/3+/jUuVS0xEQwu0WtHPXg+SMKbirNrwR6XxwUsaKVAu6MmcM8aYA5oTf1KVkZuTEbcIa36lpThYGLIT8oe2KsAV16HAHIvAe0wXFstf+cPAey7dojIFHLJbl787jcKEvgbDjA== X-YMail-OSG: P.lz.JcVM1njJM4c1MQnF5BoM0Ojpi2Fsi.ov66gMZTgofZ7sgER0cxMU6RPglk 3W_wOEgUtDLMC_GKn0KnC.Vlaqx2cJsqRFWyujy6sTdQSJ3Aj5XSDTx9uY.iiznKG_c_.IXw01Ot kWM.f3PQ9KH8.ASya8nN4H8BENeBRSUDpcD.ZA0uwb_L.iCGEnmt7hdv.rzkqkXM5JRdk.Bjq1DE bBijlsEyUjjpIhMVy_PjIOiAbRvhip2im7uCR50hiDnuiXoSjsT5Etf6ZMwf7vmbbT9Z31.RDbdm 4mIhZtWsmZNiyCiA73VlALSl20dYeZrEKxebEgStxjgQPSH.8n9kjX67P4Q3y5ztv8pkrdnOsfGs oFiS5CxPE53kOAnPOJDnycHd8c_lsF0t0z0zHCHonOjydJS8FiBsWis53D2cNkMesbB1_Pk6LgYl 0d9u02QkovW.pzrYyEh80qxPPCJCGeiNquqj__bjRPVIinoszVas82T9lC193Ry7dtYuKPoY.Ogx ucvj7BxhxCl1EY8kS5piP5s68lIuM_n00eUBl Received: from sonic.gate.mail.ne1.yahoo.com by sonic307.consmr.mail.sg3.yahoo.com with HTTP; Thu, 22 Jun 2017 12:06:03 +0000 Date: Thu, 22 Jun 2017 12:02:03 +0000 (UTC) From: Om Prakash Jaiswal Reply-To: Om Prakash Jaiswal To: "pgsql-admin@postgresql.org" Message-ID: <39669097.1721703.1498132923225@mail.yahoo.com> Subject: ERROR IN EPOCH DATA TO TIMESTAMP WITHOUT TIME ZONE MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_1721702_475809372.1498132923223" References: <39669097.1721703.1498132923225.ref@mail.yahoo.com> X-Mailer: WebService/1.1.9911 YahooMailNeo Mozilla/5.0 (X11; Linux x86_64; rv:50.0) Gecko/20100101 Firefox/50.0 Content-Length: 2903 List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-admin Precedence: bulk Sender: pgsql-admin-owner@postgresql.org ------=_Part_1721702_475809372.1498132923223 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit I have converted date/time to epoch value.Extract epoch from datetimedatadatetimedata is data type TIMESTAMP WITHOUT TIME ZONE.Now I conveted epoch value to TIMESTAMP WITHOUT TIME ZONE usingselect to_timestamp(epoch) Now I am getting actual value with added value of +5:30.I also used select to_timestamp(epoch) to TIME zone 'IST'THIS is also not giving correct original input data. this problem is not on Postgresql 9.0. but now on postgresql9.4.8 version this problem is getting.how resolve it? RegardsOm PrakashDBA, BANGALORE INDIA.MOB: 9035635787 ------=_Part_1721702_475809372.1498132923223 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
I have convert= ed date/time to epoch value.
Extract epoch from datetimedata
datetimedata is data type TIMESTAMP WITHOUT = TIME ZONE.
Now I conveted
epoch value to TIMESTAMP WITHOUT TIME ZONE using
select to_timestamp(ep= och)

=
Now I am= getting actual value with added value of +5:30.
I also used select to_timestamp(e= poch) to TIME zone 'IST'
THIS is also not giving correct original input data.
<= div dir=3D"ltr" id=3D"yui_3_16_0_ym19_1_1498131772145_4181">
this problem is not= on Postgresql 9.0.
but now on postgresql9.4.8 version this problem is getting.=
how reso= lve it?
<= br>
Regar= ds
Om Pra= kash
DBA,= BANGALORE INDIA.
MOB: 9035635787
------=_Part_1721702_475809372.1498132923223--