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 1qlC3f-001gOX-Lu for pgsql-general@arkaria.postgresql.org; Tue, 26 Sep 2023 17:41:15 +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 1qlC3e-00DikB-7L for pgsql-general@arkaria.postgresql.org; Tue, 26 Sep 2023 17:41:14 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qlC3d-00Dijv-SF for pgsql-general@lists.postgresql.org; Tue, 26 Sep 2023 17:41:13 +0000 Received: from mail-yw1-x112d.google.com ([2607:f8b0:4864:20::112d]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1qlC3X-006mAi-7u for pgsql-general@lists.postgresql.org; Tue, 26 Sep 2023 17:41:12 +0000 Received: by mail-yw1-x112d.google.com with SMTP id 00721157ae682-59f6e6b206fso64195367b3.3 for ; Tue, 26 Sep 2023 10:41:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1695750066; x=1696354866; darn=lists.postgresql.org; h=content-transfer-encoding:subject:from:content-language:to :user-agent:mime-version:date:message-id:from:to:cc:subject:date :message-id:reply-to; bh=GB6rXNDdr4RwU51My+5vybb/FkbuqufK0jJma2Tv94E=; b=gCGXoVsoMJ9fbEgyrRMU894wpclSZU8VFtYnw0uPVmT8jvF1HEnVqUZ25/NXrTWHuA DKygty65ZJRLoP8F8aooF/4gHPZQMT6Q/O4EZqsvAWPcXmkB192F7U0EP3fD3yzx0TBj ZIVHOQFwZ2UjNwnnYdCK5IEds/7tdYy3tKggX5VXXJiE2zXfIUgDkAAyUlgnQz0Tst7U uqB4KG3i2ZNeG+4xe4++9jcgpmXcBYoTaum2QcoDZayedoFQkvpmc2ARpmJMW4Hl8QFk s6yomNwcO3wHxCQG5iihXK3djFD22RjiHQk4C8rFyCLc1C0f9/weFr4wvXs9QmRQB8QU cfHw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1695750066; x=1696354866; h=content-transfer-encoding:subject:from:content-language:to :user-agent:mime-version:date:message-id:x-gm-message-state:from:to :cc:subject:date:message-id:reply-to; bh=GB6rXNDdr4RwU51My+5vybb/FkbuqufK0jJma2Tv94E=; b=p3txSXwS5/8LPZBogGoP6ycRo7ShnQwvD+a2GXM0YQIPymoq/2K/jk2N1B98Chbqgu S0qJwWUCksc/ACifmG6aV3QVZ/vre1fb34wEnFfgBw41w56anmSXw8Uqj++fasWIHFov 6IGkfdw1jybp051U+dOshAbYDHen9vvThqwA7Zg2NKOPxbOVUlap5yaZfd7TCWPZOZpm nOXiHsd7XezdN4NMgbgueZcbJT8vWQJUJMCz7yDQIFLvMCe1Eb2gLdjpuJ2yb6osFVs7 00yX1J9lG4ofcAQnXdAvh4rvGZj1OXXGxN1lZ5BaBWKgnWeIdmRuJ03TptzNrYNR8E6+ VEiw== X-Gm-Message-State: AOJu0YzeBIqjHhREowlkrgkh8QQ6CKQ0Y0bYR3wrw0bWrOd7iW0Pa+J5 kTstmF+Xzb2eDw195p9L+7Eqn9EhZ5g= X-Google-Smtp-Source: AGHT+IG7riYllI3q+5oruOvG1rvub7YVNr9N+pjAaeqKvFXbMFwPjaW3DvORy7pEqCBOFEqm0iz8sg== X-Received: by 2002:a05:690c:308a:b0:59f:687c:fb39 with SMTP id ez10-20020a05690c308a00b0059f687cfb39mr8179532ywb.14.1695750066238; Tue, 26 Sep 2023 10:41:06 -0700 (PDT) Received: from ?IPV6:2600:1700:bd2c:b810:fd72:b8a9:e719:a28b? ([2600:1700:bd2c:b810:fd72:b8a9:e719:a28b]) by smtp.googlemail.com with ESMTPSA id n66-20020a817245000000b005704c4d3579sm3125295ywc.40.2023.09.26.10.41.05 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 26 Sep 2023 10:41:05 -0700 (PDT) Message-ID: <9707e21e-eed3-3c06-821e-e935eab4c098@gmail.com> Date: Tue, 26 Sep 2023 12:41:05 -0500 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.11.0 To: pgsql-general@lists.postgresql.org Content-Language: en-US From: Ron Subject: Ad hoc SETOF type definition? Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Pg 9.6.24 (Yes, I know it's EOL.) This simple "programming example" function works perfectly. However, it requires me to create the TYPE "foo". CREATE TYPE foo AS (tab_name TEXT, num_pages INT); CREATE FUNCTION dba.blarge()     RETURNS SETOF foo     LANGUAGE plpgsql     AS $$     DECLARE         ret foo;         bar CURSOR FOR             select relname::text as table_name, relpages             from pg_class where relkind = 'r'             order by 1;     BEGIN         FOR i IN bar LOOP             SELECT i.table_name, i.relpages INTO ret;             RETURN NEXT ret;         END LOOP;     END; $$; Is there a way to define the SETOF record on the fly, like you do with RETURNS TABLE (f1 type1, f2 type2)? -- Born in Arizona, moved to Babylonia.