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 1rKa54-003NKa-Ho for pgsql-www@arkaria.postgresql.org; Tue, 02 Jan 2024 08:24: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 1rKa52-00EeYs-Qj for pgsql-www@arkaria.postgresql.org; Tue, 02 Jan 2024 08:24:56 +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 1rKa52-00EeYk-Fx for pgsql-www@lists.postgresql.org; Tue, 02 Jan 2024 08:24:56 +0000 Received: from relay9-d.mail.gandi.net ([2001:4b98:dc4:8::229]) by magus.postgresql.org with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rKa4v-00F7eA-TL for pgsql-www@lists.postgresql.org; Tue, 02 Jan 2024 08:24:55 +0000 Received: by mail.gandi.net (Postfix) with ESMTPSA id D7F02FF805; Tue, 2 Jan 2024 08:24:45 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=postgresfriends.org; s=gm1; t=1704183887; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=n1MAwNaSQvCt8GrWoUgy9yRox0awSc5/rdLp3SLIh60=; b=aK3ugdG1NQ9iSa1+BWTrybbFnAKfYsh7gFDwKe/mWJXHXyaHLaGYSKIQhT6c4lJI3G5dyO 4wVaaM2TTWQUtdKFXD+PdrhQ8tc0SQtzsu9/iJ7vnO9nlg8oxwoRYqJ6whLmqZ/PBHu0Zv /juFOUfDyn6hqYhaEsaPtL78P/PGZrTPb6bO4s4vpadF8yaOujsyYuU25xM+IvbcrM9LUi A7SIeCvYoCrp3gvhpio+YQABshinvR/NoxGQSKATXoszBw8m7gIvVjdLP/H/OJkGnRWn8o 0QbUSQvB+dw7zrupBP2aEjIPr3L6i3n6fDQukXGmAsOcg42HK7/btK4u8b0alg== Message-ID: <1aaa9762-5fb0-4d86-8788-62768b9b7a3e@postgresfriends.org> Date: Tue, 2 Jan 2024 09:24:45 +0100 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Describing Postgres as "object-relational" on the home page To: Benjamin Scherrey , "Jonathan S. Katz" Cc: "Karl O. Pinc" , pgsql-www@lists.postgresql.org, Bruce Momjian , Tom Lane References: <20231226131047.493259f8@slate.karlpinc.com> <20231228135446.3ba508d5@slate.karlpinc.com> <20231231114052.30eccee6@slate.karlpinc.com> Content-Language: en-US From: Vik Fearing In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-GND-Sasl: vik@postgresfriends.org List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 1/2/24 07:19, Benjamin Scherrey wrote: > 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. I am curious why you think this. What features of an object database do you think Postgres has to merit ranking high in search results? -- Vik Fearing