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

From: Ron <ronljohnsonjr(at)gmail(dot)com>
To: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: Behavior of PL/pgSQL function following drop and re-create of a table that it uses
Date: 2023-03-08 23:20:58
Message-ID: 94d5c746-60e8-3cb2-b500-1332e74a1cb4@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Bryn Llewellyn 2023-03-09 00:41:39 select (17, 42)::s.t2 into... fails with "invalid input syntax"
Previous Message Bryn Llewellyn 2023-03-08 21:29:28 Re: Behavior of PL/pgSQL function following drop and re-create of a table that it uses