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 1rIg17-00A236-Ko for pgsql-www@arkaria.postgresql.org; Thu, 28 Dec 2023 02:21:02 +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 1rIg13-00BaJy-Gr for pgsql-www@arkaria.postgresql.org; Thu, 28 Dec 2023 02:20:57 +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 1rIg13-00BaJP-5v for pgsql-www@lists.postgresql.org; Thu, 28 Dec 2023 02:20:57 +0000 Received: from mail-oo1-xc32.google.com ([2607:f8b0:4864:20::c32]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1rIg0z-00EEk2-Kn for pgsql-www@lists.postgresql.org; Thu, 28 Dec 2023 02:20:56 +0000 Received: by mail-oo1-xc32.google.com with SMTP id 006d021491bc7-594eb6215abso230914eaf.1 for ; Wed, 27 Dec 2023 18:20:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=proteus-tech.com; s=google; t=1703730051; x=1704334851; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=iP4N0LfblYa0QxRTaXuPasRCWiyDzsAXUyGfvvYhs1w=; b=J4398BjyOXBIjU5DwPjPv5IQNOvuF+ffpC9ITXwTI4sPhaMJW/DYO/G2xL7b1qm7UU 9c6slwVX3pngrWs+wt3BPLJNZ3zjSEsqUSpgAaUdg6Qb2cDKy1hYQxBYtT3QRqZZvaMQ lW+7XYD2zVoBWeya9dU/IK+/vPqlVABg5ciOBAOMTzNbdhXUMlsaH3dXrNH0zPIUGOOT PsaQPWIvLuWdOi8HHEgkVEFj60rWQgGZS2HDL9qkS0jeyyNEBIB3qsTfSj+LUuNzWW+X MCEMvd8SATHXqLVoNPL6Bs/fpBSb192CD2CqlA4L0F5mAGEwiDiCVFEeweqjrX1Za/1f S/sg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1703730051; x=1704334851; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=iP4N0LfblYa0QxRTaXuPasRCWiyDzsAXUyGfvvYhs1w=; b=ssj0pTCwl23q4Iv9hbtfcBaxII4ULu9TldedNBeiMM4bd18DPMKPxPJ2HAhMkSbNck 7C/TdUYGfCG5kVcOvsRgdUOXMj+i5hT6GksHf7w7RW3yjYC4YBbZqEMboDeh3ttr0JKH xDN2lD2TWDdm8XUgElmKb5a/WZNuE7ERm952tlK+hJd847fp3fvV6TJd/xTubhs6zBD1 Xhm6TjFmU+b8Ik0+yJcvKSbMeYJ6P5rgit/FQqdMINNFKtkj19GvxFZWipKKXQiS+g1X Hjz6IegXkp3y/uae39iM5Si66qAwsQghBc04HgadYEyuTwHIquGgf+MMAvkCnaCuuSg3 wmjA== X-Gm-Message-State: AOJu0YyuwCrWCMVWS2Po9rddFdD7lnA5oBvJ4QxNd4jd0Ai6Ugf8hyJ2 4ekNyuZUkklkdaED3v2uC72WKPwguUmlUZboiO4TeWATru/tlcvK4MordOzM X-Google-Smtp-Source: AGHT+IHg8Uk74x8+bHspquxJYYlgS3NDGmQvxve79zKckOWNNgJvasJDnTYq5Xt32FFqm8QP+cZ8sp1iRMQQ/eE4lN8= X-Received: by 2002:a05:6359:3289:b0:170:2421:fa03 with SMTP id rk9-20020a056359328900b001702421fa03mr6241379rwb.41.1703730050936; Wed, 27 Dec 2023 18:20:50 -0800 (PST) MIME-Version: 1.0 References: <20231226131047.493259f8@slate.karlpinc.com> In-Reply-To: <20231226131047.493259f8@slate.karlpinc.com> From: Benjamin Scherrey Date: Thu, 28 Dec 2023 09:20:39 +0700 Message-ID: Subject: Re: Describing Postgres as "object-relational" on the home page To: "Karl O. Pinc" Cc: pgsql-www@lists.postgresql.org Content-Type: multipart/alternative; boundary="0000000000007acb37060d8890d3" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000007acb37060d8890d3 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Postgres is a fully-relational (in that it simultaneously adheres to all of Codd's rules - something surprisingly rare) multi-paradigm database. It is multi-paradigm because it is also simultaneously a native object database and document database (JSONB support better than MongoDB), plus has ready extensions to be a first class Geodesic Database and Vector Database (ala AI) amongst others. Just because "object" has become a bad word because of idiots who jump on bandwagons and don't even understand the term does not remove its value. There are still those of us around who used Postgres before it had SQL support and understand how it works internally. Note that all this extensibility is made achievable a great deal because it *is* underneath it all an Object Database. But I agree that we could use better marketing language to express the full potential of this remarkable open source project. - - Ben Scherrey On Wed, Dec 27, 2023, 2:11=E2=80=AFAM Karl O. Pinc wrote= : > Hi, > > I don't want to start bikeshedding here but maybe > the answer is simple. > > The PG home page calls PG "object-relational". I question > whether this is useful. Unlike in the 90's, nobody is > really interested any more in object-oriented-everything > and the typical person reading the home page probably > does not know what an object-relational db is anyway. > > It may be better to just say "relational". > > In my opinion simpler is more clear and therefore better. > (If another adjective is necessary I like "advanced". I feel > it balances "powerful" and, in a sense, substitutes > for the "object" qualifer. Because PG is more than > just object-relational.) > > I am only asking whether the home page should be changed. > Changing the "object-relational" description elsewhere/everywhere > is another matter entirely. I suppose I think this because > I think the home page has a different, less sophisticated, audience. > > For my off-the-cuff mini-rant on this topic see the PostgeSQL > Wikipedia talk page: > Describing PG as relational v.s. object-relational in the lead > > https://en.wikipedia.org/wiki/Talk:PostgreSQL#Describing_PG_as_relational= _v.s._object-relational_in_the_lead > > FWIW, I know of at least 4 toggles between "relational" and > "object-relational" on the wikipedia page. (It's been just > "relational" for some time, but recently toggled back and forth. > Feel free to explain on the talk page and change it from the > current "relational" to "object-relational". I won't > undo. I wrote the talk page entry mostly to keep the > postgres-ignorant wikipedia enthusiasts from copy-pasting > from the PG home page.) > > This is not worth spending much time on but I wanted to raise > the issue, hoping it can be quickly resolved. There seems > to be no discussion in the pgsql-www mailing list archive. > > Regards, > > Karl > Free Software: "You don't pay back, you pay forward." > -- Robert A. Heinlein > > > --0000000000007acb37060d8890d3 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Postgres is a fully-relational (in that it simultaneously= adheres to all of Codd's rules - something surprisingly rare) multi-pa= radigm database. It is multi-paradigm because it is also simultaneously a n= ative object database and document database (JSONB support better than Mong= oDB), plus has ready extensions to be a first class Geodesic Database and V= ector Database (ala AI) amongst others.

Just because "object" has become a bad word because of = idiots who jump on bandwagons and don't even understand the term does n= ot remove its value. There are still those of us around who used Postgres b= efore it had SQL support and understand how it works internally. Note that = all this extensibility is made achievable a great deal because it *is* unde= rneath it all an Object Database. But I agree that we could use better mark= eting language to express the full potential of this remarkable open source= project.

=C2=A0 - - Ben= Scherrey=C2=A0

On Wed, Dec 27, 2023, 2:11=E2=80=AFAM Karl O. Pinc <= ;kop@karlpinc.com> wrote:
Hi,

I don't want to start bikeshedding here but maybe
the answer is simple.

The PG home page calls PG "object-relational".=C2=A0 I question whether this is useful.=C2=A0 Unlike in the 90's, nobody is
really interested any more in object-oriented-everything
and the typical person reading the home page probably
does not know what an object-relational db is anyway.

It may be better to just say "relational".

In my opinion simpler is more clear and therefore better.
(If another adjective is necessary I like "advanced".=C2=A0 I fee= l
it balances "powerful" and, in a sense, substitutes
for the "object" qualifer.=C2=A0 Because PG is more than
just object-relational.)

I am only asking whether the home page should be changed.
Changing the "object-relational" description elsewhere/everywhere=
is another matter entirely.=C2=A0 I suppose I think this because
I think the home page has a different, less sophisticated, audience.

For my off-the-cuff mini-rant on this topic see the PostgeSQL
Wikipedia talk page:
Describing PG as relational v.s. object-relational in the lead
https://en.wikipedia.org/wiki/Talk:PostgreSQL#Describing= _PG_as_relational_v.s._object-relational_in_the_lead

FWIW, I know of at least 4 toggles between "relational" and
"object-relational" on the wikipedia page.=C2=A0 (It's been j= ust
"relational" for some time, but recently toggled back and forth.<= br> Feel free to explain on the talk page and change it from the
current "relational" to "object-relational".=C2=A0 I wo= n't
undo.=C2=A0 I wrote the talk page entry mostly to keep the
postgres-ignorant wikipedia enthusiasts from copy-pasting
from the PG home page.)

This is not worth spending much time on but I wanted to raise
the issue, hoping it can be quickly resolved.=C2=A0 There seems
to be no discussion in the pgsql-www mailing list archive.

Regards,

Karl <kop@karlpinc.com>
Free Software:=C2=A0 "You don't pay back, you pay forward." =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0-- Robert A. = Heinlein


--0000000000007acb37060d8890d3--