Re: Is it time to retire type "opaque"? - Mailing list pgsql-hackers

From Andres Freund
Subject Re: Is it time to retire type "opaque"?
Date
Msg-id 20200306181215.7e34wqgjd6blbk4o@alap3.anarazel.de
Whole thread Raw
In response to Is it time to retire type "opaque"?  (Tom Lane <tgl@sss.pgh.pa.us>)
List 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



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Error on failed COMMIT
Next
From: Andres Freund
Date:
Subject: Re: Fastpath while arranging the changes in LSN order in logicaldecoding