Re: Is it time to retire type "opaque"?
Andres Freund <andres@anarazel.de>
From: Andres Freund <andres@anarazel.de>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-hackers@lists.postgresql.org
Date: 2020-03-06T18:12:15Z
Lists: pgsql-hackers
Hi, On 2020-03-03 12:10:15 -0500, Tom Lane wrote: > In short, I propose ripping out OPAQUE entirely. +1 > I wouldn't lobby too hard against removing the auto-shell-type hack > either, but it's not actually type-unsafe and it doesn't require > very much code to support, so the case for removing it seems a lot > weaker than that for getting rid of OPAQUE. I'm mildly in favor for for ripping those out too. I can't really imagine there's a lot of users left, and they shouldn't be hard to migrate. I don't think it'll get meaningfully fewer / easier if we just wait another two years - seeems likely that auto shell type using code isn't touched much. Greetings, Andres Freund
Commits
-
Remove the "opaque" pseudo-type and associated compatibility hacks.
- bb03010b9f07 13.0 landed