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 1rKY8W-003E9B-Sb for pgsql-www@arkaria.postgresql.org; Tue, 02 Jan 2024 06:20:25 +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 1rKY8S-00EBo4-9u for pgsql-www@arkaria.postgresql.org; Tue, 02 Jan 2024 06:20:20 +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 1rKY8R-00EBnw-Lx for pgsql-www@lists.postgresql.org; Tue, 02 Jan 2024 06:20:20 +0000 Received: from mail-oo1-xc30.google.com ([2607:f8b0:4864:20::c30]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1rKY8J-00F6aK-Vg for pgsql-www@lists.postgresql.org; Tue, 02 Jan 2024 06:20:18 +0000 Received: by mail-oo1-xc30.google.com with SMTP id 006d021491bc7-595b208a050so336068eaf.0 for ; Mon, 01 Jan 2024 22:20:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=proteus-tech.com; s=google; t=1704176409; x=1704781209; darn=lists.postgresql.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=avKVzJSvmA00jjoMhTs/oiFVrDu2IRq26q/YXhlPB9s=; b=o0tn0DZaySeChBci/eaHBNdEYpIMoDJt7Vfc+BTnz7/vmyC1TMtd8mkckw/Azv+gW0 i0uiNnG0bAEsC6Sysb63ps6Eo8rldEl89I+zwhaNvoSJDOSK9NLNf+WkORLL+spQxbbG EPhkq5/IWrHX65adcyK1Ets7hMtGuVzK+t4n0IhOna6rxYIsqL3Hh+PzaCL4XJZMMhR7 NKFPIflpRMmuyBCJXYGw3rX5xgg3LOfPpovSEPispz41tvno5F/+H1vZJAv3QrarO4uK U7cOja8c5pC9wCIjnEhNsDVNR6WKzbkZfoM+jeRAqeoNjrgMQRInX75OMsSsn+lKZuBf KwTw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1704176409; x=1704781209; h=content-transfer-encoding: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=avKVzJSvmA00jjoMhTs/oiFVrDu2IRq26q/YXhlPB9s=; b=oozq+cESGZhN+Plqdjc4XKE5+/4Q2YybPHmux6HIE1xZKCuCzb5cLS+IaE2zUaBuRL OHktGxDMQPWrmIfr1oqfFaEW2kaROvKwdCgIZQ0puyzUIvJFIYHt8MFZk5DL9UB28RMw uI3I0YU1oMuMcRNFDpudy9X1xbIJKmnHXLlIFK+tfme4+E1dBXz76OeA3a3pR9n1zfgh 79soaVAj0T9ZcohtzWRScndSct52FwgYFobotYfrgBAH6CDkDmIteaCqRxhNB7l3ZoaA 3TC9KPwVTV5NKfDvXdMtVczFVI4yx/ALQ2xBYDofCJIeOCEMAXjjaSlz+M31+V6kW4Pj /skA== X-Gm-Message-State: AOJu0YxzK2ykfu8lWWO+NZq6uS1ebZ5KlJnQz0QfOx3FAOfMfbCTZosW r1m+4BxgzQG1Q4wV6Q8cP2WqQOf0LF4XCT7PQTcOkuahsPdwAQ== X-Google-Smtp-Source: AGHT+IEqhhZblv+G0BweYixS2XFAqGVm0tvyL5dB5yAnp2H81none2bUVClGI1R/Vm8ywOnW7r28NwEF05lReL4ejpQ= X-Received: by 2002:a05:6359:4590:b0:175:4cc3:7dcc with SMTP id no16-20020a056359459000b001754cc37dccmr419466rwb.31.1704176409381; Mon, 01 Jan 2024 22:20:09 -0800 (PST) MIME-Version: 1.0 References: <20231226131047.493259f8@slate.karlpinc.com> <20231228135446.3ba508d5@slate.karlpinc.com> <20231231114052.30eccee6@slate.karlpinc.com> In-Reply-To: From: Benjamin Scherrey Date: Tue, 2 Jan 2024 13:19:58 +0700 Message-ID: Subject: Re: Describing Postgres as "object-relational" on the home page To: "Jonathan S. Katz" Cc: "Karl O. Pinc" , pgsql-www@lists.postgresql.org, Vik Fearing , Bruce Momjian , Tom Lane Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk I like the suggested text. I think it's a shame to drop the word object, however. Despite it getting a bad name amongst the academics, it's still very much in use and often quite useful. If someone's searching for an object database I believe Postgres should pop up high in the list. Why remove the term? Totally fine that it's no longer the first term ala "object-relational". -- Ben Scherrey On Mon, Jan 1, 2024 at 2:40=E2=80=AFAM Jonathan S. Katz wrote: > > To move this along, here is a patch with suggested changes on just the > homepage -- as mentioned, we'll likely need to deploy this wider, but I > want us to feel comfortable with the language before building a full > fledged patch. I took the suggestion of using two sentences in the first > paragraph. I don't think the second paragraph is quite there yet, but > this should give something to discuss. > > To make it easier to comment, here are the sentences below: > > =3D=3Dquote=3D=3D > PostgreSQL is a powerful, extensible, open source relational database > with over 35 years of active development. PostgreSQL has earned a strong > reputation for reliability, feature robustness, and performance. > > PostgreSQL can be used for a wide variety of use-cases, including > transactional and analytical workloads. PostgreSQL extensions add more > functionality to PostgreSQL, which are used to support geospatial, time > series, AI and vector queries, full-text search, distributed systems, > and many more workloads. > =3D=3Dquote=3D=3D > > Thanks, > > Jonathan