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 1ruEo1-003mgy-UK for pgsql-general@arkaria.postgresql.org; Tue, 09 Apr 2024 16:58:47 +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 1ruEo0-0082so-NZ for pgsql-general@arkaria.postgresql.org; Tue, 09 Apr 2024 16:58:44 +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 1ruEnz-0082sf-Nc for pgsql-general@lists.postgresql.org; Tue, 09 Apr 2024 16:58:44 +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 1ruEnw-0003Me-Ii for pgsql-general@lists.postgresql.org; Tue, 09 Apr 2024 16:58:43 +0000 Received: from compute6.internal (compute6.nyi.internal [10.202.2.47]) by mailfout.west.internal (Postfix) with ESMTP id 9BCA21C00127; Tue, 9 Apr 2024 12:58:37 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute6.internal (MEProxy); Tue, 09 Apr 2024 12:58:37 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aklaver.com; h= cc: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=1712681917; x=1712768317; bh=6fJEKxlI+05ESdbQtoMRLRVoZLENDCUd2hVljvcCRWM=; b= GQ7mrK2afEjFq4GIbGV4GsbwjLB97M/zybe0qqoY1Td/b44CQQuhkWmlFhMU8GS4 f+KaOwa7npl4JzwXOrOlPccoRP2aNTIZpXCgo/yAQnHPwLAAOY0E5+Yig83YNQXG DemALgF0kZhBYnqF43R6Q3f6VT7T/mRlAo0GUxvFuDOj4iJNkkn62P6kCYP8WZ+N UsEN1QkD8toGmvdBPkMxZ4jSQ6ZXT6+D8bc5TP1P4MbMK9CPIZMvq8sQHOTXvaYE V514xcm8+mAfhmmpF8VX5KvpQEOaGPkZWImrbpm0ZvLPO27B2yiTcYVMyw2DiBE0 yQ8dmNw7tBMGZwgXcf//nw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc: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=1712681917; x= 1712768317; bh=6fJEKxlI+05ESdbQtoMRLRVoZLENDCUd2hVljvcCRWM=; b=S SJToLoRl/CWpOsm1SycVx+jvdoQUgRffHL2uZ6svUvV+qyxq09K/5yhn9IVN2j// S0UnfdE3sJ4XwMqp8CTqHyVjTYEgqiCYwd76s8GxByO9CCmHj04VembBT+dk23TW 6xW0HM97Udn0IFLwgjD9Pt744j2Xv3ZuThRqg1gyhDtiJXcOASgqLmFS8fc8RHZM hmjKvbjYzpPx2B/QyprcyvJGFZ6fPmUpA6fuUicsLRaa9GZzvPvitAKxniNBZkxX F30UyCUoVgSVvGZExO1RBEpGpIcgxuavUJCsr8ry0/qnxXUoeGBZ7O1bOck2f0iU 8vJ44xmxhYcJlYH06f1jQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvledrudehfedgudehucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefkffggfgfuvfevfhfhjggtgfesth ekredttddvjeenucfhrhhomheptegurhhirghnucfmlhgrvhgvrhcuoegrughrihgrnhdr khhlrghvvghrsegrkhhlrghvvghrrdgtohhmqeenucggtffrrghtthgvrhhnpeefgeefie eutdfggfetgefgheekjeehteeileeigfetieekjedvieeviefgheevtdenucevlhhushht vghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpegrughrihgrnhdrkhhlrg hvvghrsegrkhhlrghvvghrrdgtohhm X-ME-Proxy: Feedback-ID: i76984098:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Tue, 9 Apr 2024 12:58:36 -0400 (EDT) Message-ID: <83c8ab4b-7b34-4b89-911d-61f38fccb9e7@aklaver.com> Date: Tue, 9 Apr 2024 09:58:34 -0700 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Issue with date/timezone conversion function To: Lok P Cc: 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 9:16 AM, Lok P wrote: > > On Tue, Apr 9, 2024 at 9:26 PM Adrian Klaver > wrote: > > 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? > > > > Thank you for the quick response. > > The column data type for "create_timestamp" is "timestamptz'. > Show timezone from the support users client machine UI showing > "Asia/Calcutta". > Not having access to run "Show timezone" on the server currently, I will > try to get it. > output from pg_setting showing setting as "Asia/Calcutta', reset_val as > "Asia/Calcutta", boot_val as "GMT" In the pg_settings query what are the source, sourcefile, sourceline fields set to? -- Adrian Klaver adrian.klaver@aklaver.com