| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Garfield Lewis <garfield(dot)lewis(at)lzlabs(dot)com> |
| Cc: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, PostgreSQL mailing lists <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: [EXT] Re: Can we get the CTID value |
| Date: | 2022-01-20 17:52:27 |
| Message-ID: | 890419.1642701147@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Garfield Lewis <garfield(dot)lewis(at)lzlabs(dot)com> writes:
> I need the page and possibly row of the data location to be stored as an element of the new type. This is to simulate a structure from another database system.
You need to rethink. The datatype input function cannot know even that
the value is going to be stored anywhere, let alone exactly where.
Moreover, what would happen if the row is moved somewhere else due
to an update of some other column?
You might be able to build something for cross-linking by putting
the logic in AFTER INSERT/UPDATE/DELETE triggers, but I think a
custom datatype is not going to be helpful for that.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Shaozhong SHI | 2022-01-20 17:54:42 | psql does not provide proper response |
| Previous Message | Vijaykumar Jain | 2022-01-20 17:38:59 | Re: Query on postgres_fdw extension |