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 1tcWwp-000lPE-Ea for pgsql-general@arkaria.postgresql.org; Mon, 27 Jan 2025 21:47:11 +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 1tcWwn-00EzaA-Ik for pgsql-general@arkaria.postgresql.org; Mon, 27 Jan 2025 21:47:09 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tcWwn-00Eza2-8F for pgsql-general@lists.postgresql.org; Mon, 27 Jan 2025 21:47:09 +0000 Received: from fout-a3-smtp.messagingengine.com ([103.168.172.146]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1tcWwk-001pZZ-10 for pgsql-general@postgresql.org; Mon, 27 Jan 2025 21:47:08 +0000 Received: from phl-compute-09.internal (phl-compute-09.phl.internal [10.202.2.49]) by mailfout.phl.internal (Postfix) with ESMTP id 6AB9D1380189; Mon, 27 Jan 2025 16:47:05 -0500 (EST) Received: from phl-mailfrontend-01 ([10.202.2.162]) by phl-compute-09.internal (MEProxy); Mon, 27 Jan 2025 16:47:05 -0500 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=fm2; t=1738014425; x=1738100825; bh=AYoroCVpVwmtf0iKqd9wzMc+a0v1PhnjHXT1l3HoCgQ=; b= SX4wdeoLRQM1dDu/Y10BKALoVpAuDxBeBwYrfH2/UhWousvpVI4Yt9fF0kW2EYhV Lo+cu+NotEXlgWIQlekV5ScxSmUN9lQq7E+kqSXR+oJNPQoCDNzwPv7mn2abhYhm P4+uMW0uOmP4KIetJblZYQ/6yifKScZ3MolWUak/fYsqTiOF6Ps30eWYGstK3wMt hmlCYzPGDvgE4UDNfCRLHAhdj5KBkA592+CfhZx97X6ivzs0WK9sJVCeUQkuIGDH 7cnNRMJYrrss73kADDbs5oqwdWLd9ovxkOnCJH3l9fX8qniPCVJ3Vak/vQiz4IVP idRJ528boZgpyGm6qsQE/g== 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-sender:x-me-sender:x-sasl-enc; s=fm3; t=1738014425; x= 1738100825; bh=AYoroCVpVwmtf0iKqd9wzMc+a0v1PhnjHXT1l3HoCgQ=; b=c eNRsyaHyrW4SOVws1SO9vPYZ5l1EVfyjbiVA5dgcppYmQb8K4ghKmFCUiUXt+toP PWJDh/nJJBVvSg38hZlNs3DDf/4aY3cda6f+yCPHFIG4luncgA//yIMmiauwesCi miUWlEyIymd7bhuD8S7cmnNwVPrgBFeHh4WjFfNcn3uD6LF5pUzdBDoUrlapR0MY yPiKN5yE0VYtrT7RwxWisPHsLHFQbDG0i+eKdUu8cnflEw7RJCtRaTJz159wUAzB TISC19TkuZoXrhZ8MKOBDdGxdfm7S4uS2ybM60QGRRtJY3IxD9/APTD55dgiUXJ8 y5gAFOpgsWsEsM0LiLO+A== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeefuddrudejgedgudegfedtucetufdoteggodetrf dotffvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdggtfgfnhhsuhgsshgtrhhisggv pdfurfetoffkrfgpnffqhgenuceurghilhhouhhtmecufedttdenucenucfjughrpefkff ggfgfuvfhfvefhjggtgfesthejredttddvjeenucfhrhhomheptegurhhirghnucfmlhgr vhgvrhcuoegrughrihgrnhdrkhhlrghvvghrsegrkhhlrghvvghrrdgtohhmqeenucggtf frrghtthgvrhhnpeetieeuleehfefhjeevfefghfeuuefgueegtdeuhfejtedvtdffvdfh tddtffelveenucffohhmrghinhepphhoshhtghhrvghsqhhlrdhorhhgpdhsthgrtghkvg igtghhrghnghgvrdgtohhmpdhsthgrtghkohhvvghrfhhlohifrdgtohhmnecuvehluhhs thgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomheprggurhhirghnrdhklh grvhgvrhesrghklhgrvhgvrhdrtghomhdpnhgspghrtghpthhtohepvddpmhhouggvpehs mhhtphhouhhtpdhrtghpthhtohepvghllhgvnhgrlhhlhhgrthgrthhlrghnsehgmhgrih hlrdgtohhmpdhrtghpthhtohepphhgshhqlhdqghgvnhgvrhgrlhesphhoshhtghhrvghs qhhlrdhorhhg X-ME-Proxy: Feedback-ID: i76984098:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon, 27 Jan 2025 16:47:04 -0500 (EST) Message-ID: Date: Mon, 27 Jan 2025 13:47:04 -0800 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Issues with EPOCH-s, TIMESTAMP(TZ)-s and leap seconds. To: Nem Tudom References: <5c09e4b5-1b00-41e6-a56c-ce1c10a3f1de@aklaver.com> Content-Language: en-US Cc: pgsql-general From: Adrian Klaver In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 1/27/25 13:23, Nem Tudom wrote: Reply to list also. Ccing list. See post from Peter Holzer . > > > Hi Adrian, all, > > >>> Any help, advice, recommendations, URL-s, references &c. appreciated. > >> https://www.postgresql.org/docs/current/functions-datetime.html >> https://www.postgresql.org/docs/current/view-pg-timezone-names.html > >> " (Technically, PostgreSQL does not use UTC because leap seconds are >> not handled.)" > > Well, that was sweet and to the point! :-) Thanks for your input! > > Does this cause any issues interfacing with other systems? > > Hmmm... it appears not: > > https://dba.stackexchange.com/questions/105514/leap-second-in-database-system-postgresql-and-sql-server > > and > > https://stackoverflow.com/questions/31136211/how-to-handle-leap-seconds-in-oracle > > So, it would appear that neither Oracle nor Microsoft (RDBMS or OS/SQL > Server) worry too much about this, so it would appear that I shouldn't > either. > > However, I think this means that there's 27 seconds of my life that I > never knew I had... > > Thanks again, saves me some work, and rgs, > > > E... > > > > -- Adrian Klaver adrian.klaver@aklaver.com