Re: Retroactively adding send and recv functions to a type? - Mailing list pgsql-general

From Tom Lane
Subject Re: Retroactively adding send and recv functions to a type?
Date
Msg-id 16030.1566313393@sss.pgh.pa.us
Whole thread Raw
In response to Re: Retroactively adding send and recv functions to a type?  (Stephen Frost <sfrost@snowman.net>)
List pgsql-general
Stephen Frost <sfrost@snowman.net> writes:
> * Vik Fearing (vik.fearing@2ndquadrant.com) wrote:
>> We generally discourage updating the catalogs directly.  This was why I
>> wrote the CREATE/ALTER DATABASE patch in 2014 that you helped me with
>> (fbb1d7d73f8).
>> I'm willing to work on a patch for ALTER TYPE if it has a chance of
>> being accepted.

> Seems pretty clear that it'd be a useful thing to have, so +1 from me,
> at least.

We'd have to be extremely circumspect about what aspects of a base
type could be altered after-the-fact.  Adding binary I/O functions
seems unproblematic, but I'm not very sure what else is.

            regards, tom lane



pgsql-general by date:

Previous
From: Adrian Klaver
Date:
Subject: Re: pg_dump problems: [archiver (db)] query failed: ERROR: relation"pg_opfamily" does not exist
Next
From: Adrian Klaver
Date:
Subject: Re: pg_dump problems: [archiver (db)] query failed: ERROR: relation"pg_opfamily" does not exist