| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Is it time to retire type "opaque"? |
| Date: | 2020-03-03 23:39:26 |
| Message-ID: | 10245.1583278766@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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
| Attachment | Content-Type | Size |
|---|---|---|
| 0001-simplify-CREATE-TYPE-1.patch | text/x-diff | 21.6 KB |
| 0002-remove-remaining-traces-of-OPAQUE-1.patch | text/x-diff | 16.8 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2020-03-03 23:44:16 | Re: Back-patching -Wno-format-truncation. |
| Previous Message | David Steele | 2020-03-03 23:37:36 | Cast to uint16 in pg_checksum_page() |