MIME-Version: 1.0
References: <01020197369aac89-01a7b7b4-b775-471e-ac8e-de8b28d87008-000000@eu-west-1.amazonses.com>
In-Reply-To: <01020197369aac89-01a7b7b4-b775-471e-ac8e-de8b28d87008-000000@eu-west-1.amazonses.com>
From: PetSerAl <petseral@gmail.com>
Date: Thu, 5 Jun 2025 20:09:21 +0300
Message-ID: <CAKygsHSmiDzcXSruEjR2XSbyF9WP2Ro3ni5utWS+XAGScJd8EQ@mail.gmail.com>
Subject: Re: Combining scalar and row types in RETURNING
To: "Ray O'Donnell" <ray@rodonnell.ie>
Cc: PostgreSQL <pgsql-general@postgresql.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://www.postgresql.org/message-id/CAKygsHSmiDzcXSruEjR2XSbyF9WP2Ro3ni5utWS%2BXAGScJd8EQ%40mail.gmail.com>
Precedence: bulk

> In my case, m_new_data is actually a table row type rather than plain
> "record". The row is passed on to another function which calculates the
> altered columns and logs the changes.

In my experience, to specify composite-typed receiver as one element
of INTO list, it need to be column of composite variable.

CREATE TABLE t (a int, b int, c int);
CREATE TYPE wrap AS (v t);
DO $DO$
  DECLARE
    s text;
    w wrap;
  BEGIN
    INSERT INTO t VALUES (1, 2, 3)
    RETURNING 'text', t
    INTO s, w.v;
    RAISE '%, %', s, w.v;
  END;
$DO$;

https://dbfiddle.uk/e5Q4Fj6l