Re: Is it time to retire type "opaque"?

Tom Lane <tgl@sss.pgh.pa.us>

From: Tom Lane <tgl@sss.pgh.pa.us>
To: pgsql-hackers@lists.postgresql.org
Date: 2020-03-03T23:39:26Z
Lists: pgsql-hackers

Attachments

I wrote:
> In short, I propose ripping out OPAQUE entirely.

Like so...

I separated out the changes in CREATE TYPE because that's a bit
more complicated than the rest.  The behavior around shell types
gets somewhat simpler, and I moved the I/O function result type
checks into the lookup functions to make them all consistent.

			regards, tom lane

Commits

  1. Remove the "opaque" pseudo-type and associated compatibility hacks.