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 1qLTnG-003Ent-KG for pgsql-sql@arkaria.postgresql.org; Mon, 17 Jul 2023 19:22: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 1qLTnF-00Dzik-1D for pgsql-sql@arkaria.postgresql.org; Mon, 17 Jul 2023 19:22:01 +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 1qLTnE-00Dzfx-Os for pgsql-sql@lists.postgresql.org; Mon, 17 Jul 2023 19:22:00 +0000 Received: from mail-lj1-x229.google.com ([2a00:1450:4864:20::229]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1qLTnA-0017ME-6e for pgsql-sql@lists.postgresql.org; Mon, 17 Jul 2023 19:22:00 +0000 Received: by mail-lj1-x229.google.com with SMTP id 38308e7fff4ca-2b6f943383eso71492131fa.2 for ; Mon, 17 Jul 2023 12:21:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1689621715; x=1692213715; h=cc:to:subject:message-id:date:from:references:in-reply-to :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=qo30/mVChlF6up28o0T5f8NZ562TJ225KSHZ2Yuqyuw=; b=Xvf9nt/zJ2ulAbCp13m/YPLVFPHHPjQk9cx/Sy0a/IYEJHCe03DCqJLduv5b0zG1Pm 8TyHCAXhZFEiLLjao0N8ilwFKiFED6oCIn509fkTEqx9YCyDUe+E3odCdEGufiC1Ya/B 7AlM1QzggdhYULJ+6+j5PIQhPM41lA5so0ltru97BXlSi9qB+07P3m9lmFETRcnTOA+h wxwsmlVPgOw4/Twp0e28dS9bTFZFj3WGBoekFkGIlGOUeB1kqisf+7L8NEwDg6AvoAkq a3+jHxy1vHITGdZwrSQ4OG5LBczC6hIfVZ0n39qLnQ7bwFlrLsmvzMOQfMQphc1mmsl+ 8YnA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1689621715; x=1692213715; h=cc:to:subject:message-id:date:from:references:in-reply-to :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=qo30/mVChlF6up28o0T5f8NZ562TJ225KSHZ2Yuqyuw=; b=eN78p2vlzClDxt/YkS24BxoQMtt5vGGbVg1d9E/e4RU30ZJwVdpE+8OBsfJqOfJrA8 uGGuu0O8dqfbKhaMCppaAn79K2wLXIrcoDOTrskbsRUoy7zn2fNlOQV4wefC1BVuP9Zz 0ogxGYQEZDTqyzPf64lxOyFcqY8smbz6tylQPzaowLDqEKWk15LI6ekiQswNLUIzmdtk dWhKKpGPTFFnHKQ1MAqo4yJjPXFL950HFDkp397ZN2TG8HfSEXQK3hbr9/yny8Wa//Dz /5jM9/KcpUxHq/vXnPeUwb/DcZET7mhi/sc5+S9GH6vYuYcXlUwwCeNqnv3o52f7fW4d 0g/A== X-Gm-Message-State: ABy/qLYtxBWVqr/53ILFPLcjOVl3qddk8rDUwyYVY6lyvuMvgYQmiKKO fwstAKal2Z8TxySrL4D53u/EumLgreh/emP/MjU= X-Google-Smtp-Source: APBJJlEJu60eh823FZnGGNNKt/+yF3e+e0PcUymgHw43SdDhq7EWua5OAZgGsIUMqmfPXVmGLXPnA2kg6YrxasMjY3c= X-Received: by 2002:a2e:9792:0:b0:2b6:eb5c:e23c with SMTP id y18-20020a2e9792000000b002b6eb5ce23cmr9596459lji.34.1689621714695; Mon, 17 Jul 2023 12:21:54 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a17:907:1c0f:b0:992:6de4:aed9 with HTTP; Mon, 17 Jul 2023 12:21:54 -0700 (PDT) In-Reply-To: References: From: Shaozhong SHI Date: Mon, 17 Jul 2023 20:21:54 +0100 Message-ID: Subject: Re: Multiple sets of results from recursive query To: Greg Sabino Mullane Cc: pgsql-sql Content-Type: multipart/alternative; boundary="0000000000001bfa8e0600b3b6b5" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000001bfa8e0600b3b6b5 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Monday, 17 July 2023, Greg Sabino Mullane wrote: > What exact problem are you trying to solve? Recursive CTEs return one > row per internal invocation, so they already return a "set" of results, b= ut > you could use arrays or json if you wanted to pack in extra information p= er > returned row. > > On Sun, Jul 16, 2023 at 6:41=E2=80=AFAM Shaozhong SHI > wrote: > >> Has anyone come across multiple sets of results with recursive query? >> >> How to handle it=EF=BC=9F >> > Surely=EF=BC=8C there must be possible to find all route paths. Regards, David --0000000000001bfa8e0600b3b6b5 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

On Monday, 17 July 2023, Greg Sabino Mullane <htamfids@gmail.com> wrote:
What exact problem are you trying to solve? = Recursive CTEs return one row=C2=A0per internal invocation, so they already= return a "set" of results, but you could use arrays or json if y= ou wanted to pack in extra information per returned row.

On Sun, Jul 16, 202= 3 at 6:41=E2=80=AFAM Shaozhong SHI <shishaozhong@gmail.com> wrote:
Has anyone c= ome across multiple sets of results with recursive query?

How to handle it=EF=BC=9F

Surely=EF=BC=8C there must be possible to find all route pa= ths.

Regards, David=C2=A0
--0000000000001bfa8e0600b3b6b5--