| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Marthin Laubscher <postgres(at)lobeshare(dot)co(dot)za> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Custom type's modifiers |
| Date: | 2024-06-27 16:12:25 |
| Message-ID: | CAKFQuwZnhZPQgbL687qeT5sC3kjWJ4r9QQwqB1nU5xtLbOj=HQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Jun 27, 2024 at 8:49 AM Marthin Laubscher <postgres(at)lobeshare(dot)co(dot)za>
wrote:
>
> I suppose when a cast is involved it goes via the external format as well,
> right?
>
A cast between two types is going to accept a concrete instance of the
input type, in memory, as its argument and then produces a concrete
instance of the output type, in memory, as output. If the input data is
serialized the constructor for the input type will handle deserialization.
See: create cast
https://www.postgresql.org/docs/current/sql-createcast.html
In particular the phrasing: identical to or binary-coercible to
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2024-06-27 16:18:31 | Re: JIT causes core dump during error recovery |
| Previous Message | Marthin Laubscher | 2024-06-27 15:49:08 | Re: Custom type's modifiers |