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 1sKgZA-00BbWI-Sn for pgsql-general@arkaria.postgresql.org; Fri, 21 Jun 2024 15:52:45 +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 1sKgZ9-003yv4-69 for pgsql-general@arkaria.postgresql.org; Fri, 21 Jun 2024 15:52:43 +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 1sKgZ8-003yuw-NT for pgsql-general@lists.postgresql.org; Fri, 21 Jun 2024 15:52:43 +0000 Received: from mail-oi1-x234.google.com ([2607:f8b0:4864:20::234]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sKgZ6-002qnS-C5 for pgsql-general@lists.postgresql.org; Fri, 21 Jun 2024 15:52:42 +0000 Received: by mail-oi1-x234.google.com with SMTP id 5614622812f47-3d21c4eec2dso1052539b6e.1 for ; Fri, 21 Jun 2024 08:52:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1718985158; x=1719589958; 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=fjDq3Lw9FaPQLmNL0z0UELxPO+xedGYZ9r2PXNV/CPc=; b=lxAl/dguJbWNgS3HgWePOATgRQ/SSgQmGItmfHw6+tyM6YEb/WWnc/tNqYKSAdsE8j RT9L8qFuwnlxh4R2WaPlbqRS7fY5dUF/Xc7wPbXgsSbW+ubj9Box2bZukPeZpt8VVvwP nkEQQmDkS4llBr4kRZxoaQ60dJ82wVxE20s+2r2giHA4umMDtINB//kNIT0sy5m2lpY+ cpkaIlQzxMyyQ6axX/vusRly9iNM+MQnMQLq9vj0chmLdbzoAvgefwnXOSZmssSuse9e OU3tViif6r5IE0AFXpP1WyvSU/HnIbRzqJpIGboM7IhQYi1qmlDjchsl9fYgPGaa6rHL mPAw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1718985158; x=1719589958; 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=fjDq3Lw9FaPQLmNL0z0UELxPO+xedGYZ9r2PXNV/CPc=; b=pjwJnwzrR3IT0Hmq5944ffBWsHIeHqhQ12WIzrDRx/JJ8bZOQpVT/ogGEoGoTCbdJf g04ydvMeBj3uwjqd2V7c1yRUijGXlTI9Z/WL2WGcu0FY9s3+3p0aBK/r21RzEImzjljO yiiYTyXCaa7yLjrCQKpNgEQIXIF2UysynZVSTpbROk7WfuQMnC6TWnFbb9UzlPmGZb9b j+8VRAyHc+FaoTaWB8FBgqmXlRrKCTutgsRD7eZNAwk+FRzz9eEt+P1xlnp952hjFHM1 gsQE14L1LyTt1mLl4e0neQtZ4ZiFa0cONVaH04rHLfsfza6AjO1873JI6y0K/w5lI/CC Rc9w== X-Gm-Message-State: AOJu0Yy1Pu+GhtNc48uir4m02MZ+dJQ+1MESQLL16ns8tMUTW+kjUFDj TTlQEuDio/mZAdIF4VVTrDMmLtj5ghdd5677oEt3AT0DxTWQxWEz6aGZVZBCkzlpolTvMV7nfQw 7Un9jCONiMtN44NmeIJu9xyBTQiuGVGar X-Google-Smtp-Source: AGHT+IHHilitZ7vaNKcQTP1u6FYSuqoiebn1jKytFw1WGXQnugyDXa3G4JcrayKpFssWzFAR1tk+uK+3cMofHujD5MY= X-Received: by 2002:a05:6808:bcb:b0:3d2:20e2:3695 with SMTP id 5614622812f47-3d51baf0722mr8332708b6e.56.1718985158391; Fri, 21 Jun 2024 08:52:38 -0700 (PDT) MIME-Version: 1.0 References: <3528232.1718682678@sss.pgh.pa.us> In-Reply-To: From: "David G. Johnston" Date: Fri, 21 Jun 2024 08:52:00 -0700 Message-ID: Subject: Re: RowDescription for a function does not include table OID To: Maxwell Dreytser Cc: "pgsql-general@lists.postgresql.org" Content-Type: multipart/alternative; boundary="000000000000bd8036061b686b64" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000bd8036061b686b64 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Fri, Jun 21, 2024 at 8:41=E2=80=AFAM Maxwell Dreytser < Maxwell.Dreytser@assistek.com> wrote: > On Friday, June 21, 2024 11:28 AM David G. Johnston < > david.g.johnston@gmail.com> wrote: > > > In short, the system doesn't generate the information you need, where > you need it, to tie these pieces together. Modifying existing elements o= f > the backend protocol is not presently in the cards. > > From my perspective this is clearly a bug as there is no way to define a > function in a way that provides enough data to the reader. > Quick search turned up this prior thread: https://www.postgresql.org/message-id/19323.1245720832%40sss.pgh.pa.us Based upon that unargued point the only bug here is in the documentation, leaving the reader to assume that some effort will be made to chain together a function returns clause to a physical table through that table's automatically-generated composite type. We don't and never will modify the existing protocol message semantics in that respect. David J. --000000000000bd8036061b686b64 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Fri, Jun 21, 2024 at 8:41=E2=80=AFAM Maxwell Dreytser &= lt;Maxwell.Dreytser@assist= ek.com> wrote:
On Friday, June 21, 2024 11:2= 8 AM David G. Johnston <david.g.johnston@gmail.com> wrote:

> In short, the system doesn't generate the information you need, wh= ere you need it, to tie these pieces together.=C2=A0 Modifying existing ele= ments of the backend protocol is not presently in the cards.

From my perspective this is clearly a bug as there is no way to define a fu= nction in a way that provides enough data to the reader.

Quick search turned up this prior thread:

https://www.postgresql.org/message-id/19323.1245= 720832%40sss.pgh.pa.us

Based upon that unargue= d point the only bug here is in the documentation, leaving the reader to as= sume that some effort will be made to chain together a function returns cla= use to a physical table through that table's automatically-generated co= mposite type.=C2=A0 We don't and never will modify the existing protoco= l message semantics in that respect.

David J.
=
--000000000000bd8036061b686b64--