Re: Proposal: stand-alone composite types - Mailing list pgsql-hackers

From Thomas Lockhart
Subject Re: Proposal: stand-alone composite types
Date
Msg-id 3D545DB6.6C3FF8A1@fourpalms.org
Whole thread Raw
In response to Re: Proposal: stand-alone composite types  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers
> That's what I was thinking. In cases where you want to use the type for
> several functions, use CREATE TYPE. If you only need the type for one
> function, let the function creation process manage it for you.

It would be nice then to have some mechanism for converting the
"automatic type" to a named type which could be used elsewhere.
Otherwise one would need to garbage collect the separate stuff later,
which would probably go into the "not so convenient" category of
features...
                  - Thomas


pgsql-hackers by date:

Previous
From: Scott Shattuck
Date:
Subject: strange performance anomalies
Next
From: Joe Conway
Date:
Subject: Re: Proposal: stand-alone composite types