Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1ruDr4-003d6L-I0 for pgsql-general@arkaria.postgresql.org; Tue, 09 Apr 2024 15:57:51 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1ruDq4-0071WI-VY for pgsql-general@arkaria.postgresql.org; Tue, 09 Apr 2024 15:56:48 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1ruDq4-0071W9-0a for pgsql-general@lists.postgresql.org; Tue, 09 Apr 2024 15:56:48 +0000 Received: from wfout4-smtp.messagingengine.com ([64.147.123.147]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1ruDpw-0002mV-7p for pgsql-general@lists.postgresql.org; Tue, 09 Apr 2024 15:56:46 +0000 Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailfout.west.internal (Postfix) with ESMTP id A14D81C00103; Tue, 9 Apr 2024 11:56:36 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Tue, 09 Apr 2024 11:56:36 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aklaver.com; h= cc:content-transfer-encoding:content-type:content-type:date:date :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to; s=fm1; t=1712678196; x=1712764596; bh=WFaHCoTvhMwTMdT7FYg9vqSM1aVG2o6vHvIyQXV2P+0=; b= noHM/kKr62fTw7ABBke5aTCn4BKTAWsE9Kha8oso9VhIDQvWXUiLEcvmnEGqtTRu aq9sqLbZte78vffFYa9baShk7/0KTtjWiwgOi0yUZb5X/ufI5X2g0hrIcgpvCtws /xhZ4xkTuOREhVKlD6moXzRmObo2MwQ+VbtCoQ/t2gO9y2J7HoHftQ/484/BT7dc oIPkYpWuzpeIsniWS4w5TXrstQ3uIJ8/miY3x/KjPaW/Bc58BgEyNO2nlSXRvDVA ivGYEkW5L1F2pi3lAWXMhzHFai5CdLK4pEYHaktH8/CZdNzpMCTQppGA3nBxIhTU dHGUz/SNOgggZeWVfunnnA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm2; t=1712678196; x= 1712764596; bh=WFaHCoTvhMwTMdT7FYg9vqSM1aVG2o6vHvIyQXV2P+0=; b=R m+TUHcaj4HRvbOV2HOySXImzq/oUqKIDiwp5Zp4TNVWHKl2gSWrSIYsIhxm7LxZA e/WJr3HE14Esk32fqvw/HNiQ/zQeh3jEkFlUUZx1jiMTXLBTkvLzfpTS2rkprK0k y73+hGsdXogN78At/BApH0rQ+jVhWhqOIFWMUMC3i3OZhM7dTWM41/0Hs9M2TPWI BjKPqwoVyERvqxCzXND5QjfE5hiH+N4D2G6xD4zp48N2VI3a5qZNYGkTpH08jn+l EpPDrVXtsj9HZer5jXN1Gf2jsr46KGbmTKsdnLS8qpBDfWbCX6LXwFrW9Z3cdVE0 rRNQoG5NqOj11hEcRa8iA== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvledrudehfedgtddvucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefkffggfgfuvfhfhfgjtgfgsehtke ertddtvdejnecuhfhrohhmpeetughrihgrnhcumfhlrghvvghruceorggurhhirghnrdhk lhgrvhgvrhesrghklhgrvhgvrhdrtghomheqnecuggftrfgrthhtvghrnhepffelgeeife fgveduhedthfekuedtffejveegffegjeevtdehgfduieetfeehjeehnecuvehluhhsthgv rhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomheprggurhhirghnrdhklhgrvh gvrhesrghklhgrvhgvrhdrtghomh X-ME-Proxy: Feedback-ID: i76984098:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Tue, 9 Apr 2024 11:56:35 -0400 (EDT) Message-ID: Date: Tue, 9 Apr 2024 08:56:34 -0700 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Issue with date/timezone conversion function To: Lok P , pgsql-general References: Content-Language: en-US From: Adrian Klaver In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 4/9/24 08:43, Lok P wrote: > Hi All, > It's version 15.4 of postgresql database. Every "date/time" data type > attribute gets stored in the database in UTC timezone only. One of the > support persons local timezone is "asia/kolkata" and  that support > person needs to fetch the count of transactions from a table- > transaction_tab and share it with another person/customer who is in the > EST timezone, so basically the transaction has to be shown or displayed > the EST timezone. What is the datatype for the create_timestamp? What does SHOW timezone; return on the server? -- Adrian Klaver adrian.klaver@aklaver.com