| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | Alberto Piai <alberto(dot)piai(at)gmail(dot)com>, Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com>, Álvaro Herrera <alvherre(at)kurilemu(dot)de> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Adding a stored generated column without long-lived locks |
| Date: | 2026-09-24 10:47:05 |
| Message-ID: | f2d93a4aabc2737ecb933d4f33b0739e9921e71b.camel@cybertec.at |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, 2026-09-24 at 00:19 +0200, Alberto Piai wrote:
> I find Matthias' proposal of exposing a function to check image equality
> very compelling for the purpose of this patch: besides fixing this
> problem, it would also make the command usable for data types which
> don't define = (json), as well as those which don't (can't?) define
> equalimage()... jsonb, numeric but also tsvector and PostGIS geometry.
True, "tsvector" is limiting; I can see people wanting that for
generated columns.
Yours,
Laurenz Albe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Antonin Houska | 2026-09-24 10:55:23 | Re: REPACK enhancements |
| Previous Message | Amit Langote | 2026-09-24 10:36:41 | Re: PG19: two RI fast-path issues found while testing the batching revert |