Re: Behavior of PL/pgSQL function following drop and re-create of a table that it uses - Mailing list pgsql-general

From Ron
Subject Re: Behavior of PL/pgSQL function following drop and re-create of a table that it uses
Date
Msg-id 94d5c746-60e8-3cb2-b500-1332e74a1cb4@gmail.com
Whole thread Raw
In response to Re: Behavior of PL/pgSQL function following drop and re-create of a table that it uses  (Bryn Llewellyn <bryn@yugabyte.com>)
List pgsql-general
On 3/8/23 15:29, Bryn Llewellyn wrote:
[snip]
create table s.t(k int primary key, c1 int, c2 int, c3 int);
insert into s.t(k, c1, c2, c3) values(1, 17, 42, 57);
create type s.x as (c1 int, c2 int, c3 int);

[snip]

This is an excellent analysis.


Native PG doesn't provide much metadata or tooling to help you here. You need your own reliable humanly written external doc of your system.


"pg_dump --schema-only" and then grep for type x?

--
Born in Arizona, moved to Babylonia.

pgsql-general by date:

Previous
From: Bryn Llewellyn
Date:
Subject: Re: Behavior of PL/pgSQL function following drop and re-create of a table that it uses
Next
From: Bryn Llewellyn
Date:
Subject: select (17, 42)::s.t2 into... fails with "invalid input syntax"