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 <pgsql-docs-owner+archive@lists.postgresql.org>)
	id 1uchIe-00FtxR-L5
	for pgsql-docs@arkaria.postgresql.org; Fri, 18 Jul 2025 09:22:40 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.94.2)
	(envelope-from <pgsql-docs-owner+archive@lists.postgresql.org>)
	id 1uchIb-009pKR-Mc
	for pgsql-docs@arkaria.postgresql.org; Fri, 18 Jul 2025 09:22:38 +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 <kes-kes@yandex.ru>)
	id 1uchIb-009pKJ-Ef
	for pgsql-docs@lists.postgresql.org; Fri, 18 Jul 2025 09:22:38 +0000
Received: from forward501d.mail.yandex.net ([178.154.239.209])
	by magus.postgresql.org with esmtps  (TLS1.3) tls
 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.96)
	(envelope-from <kes-kes@yandex.ru>)
	id 1uchIZ-008Pch-1s
	for pgsql-docs@lists.postgresql.org;
	Fri, 18 Jul 2025 09:22:37 +0000
Received: from mail-nwsmtp-mxback-production-main-48.iva.yp-c.yandex.net
 (mail-nwsmtp-mxback-production-main-48.iva.yp-c.yandex.net
 [IPv6:2a02:6b8:c0c:3b1f:0:640:fb8a:0])
	by forward501d.mail.yandex.net (Yandex) with ESMTPS id 20666636E8;
	Fri, 18 Jul 2025 12:22:34 +0300 (MSK)
Received: from mail.yandex.ru (2a02:6b8:c0c:89a8:0:640:c417:0
 [2a02:6b8:c0c:89a8:0:640:c417:0])
	by mail-nwsmtp-mxback-production-main-48.iva.yp-c.yandex.net (mxback/Yandex)
 with HTTPS id WMKwDc5MuuQ0-UsIuXbEr;
	Fri, 18 Jul 2025 12:22:33 +0300
X-Yandex-Fwd: 1
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail;
	t=1752830553; bh=0oQ8W+Yzs+DMoETHzPmsYnPXX2IHZszUBm2wUUqbadM=;
	h=Message-Id:References:Date:Subject:To:In-Reply-To:From;
	b=G3kPb6NYkWD8E2Nc64r6vKf6jUiigUjfq38twjck2mDRB3D26snsavjUIFghBaxbk
	 wbZVPMHj03hiotsvEg1F4HG+MD1xBW54E3U3Ta1nM9fZO3Rx8ALY3hVsYuS8ozBaqw
	 RC7gnHnAn5Z1kYRCXUU6glPIL7h4/ldw3Fj/e+98=
Authentication-Results: 
 mail-nwsmtp-mxback-production-main-48.iva.yp-c.yandex.net;
 dkim=pass header.i=@yandex.ru
Received: by qnb4xdsvdwd5l2mw.iva.yp-c.yandex.net (sendbernar/Yandex) with
 HTTPS id ba1f06ea2872b151c278a742a65f8875;
	Fri, 18 Jul 2025 12:22:27 +0300
From: KES <kes-kes@yandex.ru>
To: David G. Johnston <david.g.johnston@gmail.com>,
	"pgsql-docs@lists.postgresql.org" <pgsql-docs@lists.postgresql.org>
In-Reply-To: 
 <CAKFQuwYasSoJjBJShcomQ76ZYEOt-UqrpTja=J7Emi5aZcgjKA@mail.gmail.com>
References: <175241302040.858619.13742825859329909914@wrigleys.postgresql.org>
 <CAKFQuwYasSoJjBJShcomQ76ZYEOt-UqrpTja=J7Emi5aZcgjKA@mail.gmail.com>
Subject: Re: Add example to sort results by two composite types
MIME-Version: 1.0
X-Mailer: Yamail [ http://yandex.ru ] 5.0
Date: Fri, 18 Jul 2025 12:22:27 +0300
Message-Id: <221161752830249@mail.yandex.ru>
Content-Transfer-Encoding: 8bit
Content-Type: text/html; charset=utf-8
List-Id: <pgsql-docs.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-docs@lists.postgresql.org>
List-Owner: <mailto:pgsql-docs-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-docs>
Archived-At: 
 <https://www.postgresql.org/message-id/221161752830249%40mail.yandex.ru>
Precedence: bulk

<div>I never saw such examples before and never thought that I can pass two composite types into ORDER BY clause. Because this section is about composite types, I found it could be useful to highlight that possibility. Otherwise it is too implicit. at least for not so experienced users like me.</div><div> </div><div> </div><div><br /></div><div><br /></div><div>----------------</div>
                        <div>Кому: kes-kes@yandex.ru (kes-kes@yandex.ru), pgsql-docs@lists.postgresql.org (pgsql-docs@lists.postgresql.org);<br /></div>
                        
                        <div>Тема: Add example to sort results by two composite types;<br /></div>
                        <div>14.07.2025, 16:58, "David G. Johnston" &lt;david.g.johnston@gmail.com&gt;:<br /></div>
                        <blockquote>On Sunday, July 13, 2025, PG Doc comments form &lt;<a href="mailto:noreply@postgresql.org">noreply@postgresql.org</a>&gt; wrote:<br /><blockquote class="f13ca48719c8a60033905b23b39675agmail_quote" style="border-left-color:#ccc;border-left-style:solid;border-left-width:1px;margin:0 0 0 0.8ex;padding-left:1ex"><br />
I suggest to extend the example to sort results by first composite type and<br />
then by the second:<br />
SELECT * FROM invertory_type t, inventory_item c ORDER BY (<a href="http://c.name/" target="_blank">c.name</a>,<br />
c.supplier_id, c.price), (<a href="http://t.name/" target="_blank">t.name</a>, t.value);<br />
<br />
Though I did not checked this if it possible or not. It would be nice to<br />
have it documented.<br />
</blockquote><div><br /></div><div>What new information does that add or uncertainty does it clarify?  This isn’t a section teaching order by - the reader is expected to already understand that an order by clause can accept two column names and how those are treated (i.e., ties among the first are broken by the second).  This is a section about how within that structure the comparisons happen.  A single column suffices to make that explanation.</div><div><br /></div><div>David J.</div><div><br /></div>
</blockquote>