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 1srfxF-003jDb-N7 for pgsql-hackers@arkaria.postgresql.org; Fri, 20 Sep 2024 15:53:58 +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 1srfxD-008q17-Bp for pgsql-hackers@arkaria.postgresql.org; Fri, 20 Sep 2024 15:53:56 +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 1srfxD-008q0z-24 for pgsql-hackers@lists.postgresql.org; Fri, 20 Sep 2024 15:53:56 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1srfxB-000CES-Pj for pgsql-hackers@postgresql.org; Fri, 20 Sep 2024 15:53:55 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 48KFrnEt2440815; Fri, 20 Sep 2024 11:53:49 -0400 From: Tom Lane To: Tomas Vondra cc: Marcos Pegoraro , pgsql-hackers Subject: Re: Why mention to Oracle ? In-reply-to: <484a27f9-dea5-4734-93d5-90fb757080bc@vondra.me> References: <484a27f9-dea5-4734-93d5-90fb757080bc@vondra.me> Comments: In-reply-to Tomas Vondra message dated "Fri, 20 Sep 2024 16:56:48 +0200" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <2440813.1726847629.1@sss.pgh.pa.us> Date: Fri, 20 Sep 2024 11:53:49 -0400 Message-ID: <2440814.1726847629@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Tomas Vondra writes: > On 9/20/24 14:36, Marcos Pegoraro wrote: >> Why PostgreSQL DOCs needs to show or compare the Oracle way of doing >> things ? > I didn't dig into all the places you mention, but I'd bet those places > reference Oracle simply because it was the most common DB people either > migrated from or needed to support in their application next to PG, and > thus were running into problems. The similarity of the interfaces and > SQL dialects also likely played a role. It's less likely to run into > subtle behavior differences e.g. SQL Server when you have to rewrite > T-SQL stuff from scratch anyway. As far as the mentions in "Data Type Formatting Functions" go, those are there because those functions are not in the SQL standard; we stole the API definitions for them from Oracle, lock stock and barrel. (Except for the discrepancies that are called out by referencing what Oracle does differently.) A number of the other references probably have similar origins. regards, tom lane