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 1rIcHc-009lrx-Kk for pgsql-www@arkaria.postgresql.org; Wed, 27 Dec 2023 22:21:48 +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 1rIcHb-00AJA2-97 for pgsql-www@arkaria.postgresql.org; Wed, 27 Dec 2023 22:21:47 +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 1rIcHa-00AJ9o-C4 for pgsql-www@lists.postgresql.org; Wed, 27 Dec 2023 22:21:47 +0000 Received: from wout3-smtp.messagingengine.com ([64.147.123.19]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rIcHX-00CVOv-DD for pgsql-www@lists.postgresql.org; Wed, 27 Dec 2023 22:21:45 +0000 Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.west.internal (Postfix) with ESMTP id 324AE320092C; Wed, 27 Dec 2023 17:21:41 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Wed, 27 Dec 2023 17:21:41 -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=fm1; t=1703715700; x=1703802100; bh=TYd6Uy+yzSiBULFkh2orPgBZq6NGAfiMGoTjLRRmJp8=; b= b9pjVKa2ePx3ZLB76ei6Xw21KtDDVZv92IABSsaf1iT2mp6ofGPuPF7cM7VqRC/I pHUrIXtAA7z6dQVrKrksoSGQPi0i422XbdBuHkeymrUkbaIg3/ZE8zaQXU0Tcwcq 0QE2CIym7kcRThzLVWx1Ntwau8oH2CDj5VuFVpbVPdMeQBMzqUp0fDKqJ3+MVdEe SGKRCc1T9pAiyN3WPoBFGVkCWBu8No5Gnz7jXIqg345AChZgp+7lu9YlWgjNcdoI 4kjfRfCNND/Qi7toYko0dueV9/c7275uDFVRbhtT4NXKsDmegNznPcQahZk5zNqE 9xRG+xLd7seGcgFSKZFSZQ== 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=1703715700; x= 1703802100; bh=TYd6Uy+yzSiBULFkh2orPgBZq6NGAfiMGoTjLRRmJp8=; b=B gnnd8rOC4A0PajhcKzNLYiUYbxPxOa+Yqhp5yk10uecPK4V3KfZBWkOxiJfckpQr F47Eu9mbtNYPRdYfY9nhTKY/OGDES4szWGmBLw3U/NqujttrMXn4HQmBGUO/hSuI kB0sYhkOWAmGpzUS/hOKElvtlIzTu/jXACyG+cNd+DcZuzbhn4M5UX/tDFfpXcU5 a8fX1UFfR8O+REnmu1c9UClHWFl9RYuasYVHBh8VNW7CB2jmq9XRoeZeB5a9K5rA R7UOgvEsBNo2T6uEna2lyeBgh/Gu0s+ZoJzxyeoaKjn9ZXBuCvMi52y4GXL7Tn8U Jip+vWwx9uk/84gOXop+A== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvkedrvddvledgudeivdcutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpefkffggfgfuvfevfhfhjggtgfesthekredttddvjeenucfhrhhomheptegu rhhirghnucfmlhgrvhgvrhcuoegrughrihgrnhdrkhhlrghvvghrsegrkhhlrghvvghrrd gtohhmqeenucggtffrrghtthgvrhhnpeduffdvjefgtefghfehkefhieduiedvueffueeh leffvedvudekheegteeuvddttdenucffohhmrghinhepfihikhhiphgvughirgdrohhrgh enucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpegrughr ihgrnhdrkhhlrghvvghrsegrkhhlrghvvghrrdgtohhm X-ME-Proxy: Feedback-ID: i76984098:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 27 Dec 2023 17:21:39 -0500 (EST) Message-ID: <65d0b719-a0f8-4f82-8bf7-2c99aae510a5@aklaver.com> Date: Wed, 27 Dec 2023 14:21:38 -0800 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Describing Postgres as "object-relational" on the home page To: "Jonathan S. Katz" , Bruce Momjian , Vik Fearing Cc: Tom Lane , "Karl O. Pinc" , pgsql-www@lists.postgresql.org References: <20231226131047.493259f8@slate.karlpinc.com> <2321548.1703625666@sss.pgh.pa.us> <286d0148-0fd0-49ff-ae85-d0628674f63f@postgresfriends.org> <8b836cca-faf5-4795-8def-55e12f364a54@postgresql.org> Content-Language: en-US From: Adrian Klaver In-Reply-To: <8b836cca-faf5-4795-8def-55e12f364a54@postgresql.org> 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 12/27/23 13:53, Jonathan S. Katz wrote: > On 12/26/23 5:40 PM, Bruce Momjian wrote: >> On Tue, Dec 26, 2023 at 10:49:16PM +0100, Vik Fearing wrote: >>> On 12/26/23 22:21, Tom Lane wrote: >>>> Bruce Momjian writes: >>>>> On Tue, Dec 26, 2023 at 01:10:47PM -0600, Karl O. Pinc wrote: >>>>>> It may be better to just say "relational". >>>> >>>>> I guess if I had to name this with no precedence, I would call it >>>>> relational/extendable, but that seems even worse that what we have. >>>> >>>> Call it an "extensible relational database"?  I agree that the >>>> "object" part is out of date and no longer much of a focal point. >>> >>> Especially considering we hardly implement any of the object features at >>> all.  We have table inheritance, and that's about it. >> >> "extensible relational database" works for me. > > Reading [1], I can align with dropping "object-" from the text. > > Currently -1 on swapping it with "extensible", given most folks describe > PostgreSQL as a relational database. > > That said, I do personally describe one of PostgreSQL's best attributes > to be its "extensibility," so I could warm up to incorporating it into > "official verbiage" in the coming days. Reading this I got a vision of a cat in a box:) At some point the state has to resolve. Are you indicating that "extensible relational database" is acceptable to you? > > Jonathan > > [1] https://en.wikipedia.org/wiki/Object%E2%80%93relational_database > -- Adrian Klaver adrian.klaver@aklaver.com