| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Is it time to retire type "opaque"? |
| Date: | 2020-03-06 18:12:15 |
| Message-ID: | 20200306181215.7e34wqgjd6blbk4o@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2020-03-06 18:13:25 | Re: Fastpath while arranging the changes in LSN order in logical decoding |
| Previous Message | Robert Haas | 2020-03-06 18:12:10 | Re: Error on failed COMMIT |