| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Residual tsquery cleanups |
| Date: | 2026-08-16 16:21:59 |
| Message-ID: | 455079.1786897319@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
The two attached, pretty trivial patches clean up some loose ends
from the recent tsvector/tsquery security commits. I'm thinking
of back-patching both, but perhaps there is an argument for not
back-patching the first one?
regards, tom lane
| Attachment | Content-Type | Size |
|---|---|---|
| v1-0001-Tighten-up-tsqueryrecv.patch | text/x-diff | 1.8 KB |
| v1-0002-Clean-up-documentation-about-text-search-datatype.patch | text/x-diff | 2.5 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | mailinglists | 2026-08-16 16:48:48 | pg_upgrade from pg19 source build to pg19-beta3 throws an error |
| Previous Message | Álvaro Herrera | 2026-08-16 16:21:33 | Re: pgcrypto.sgml: built in -> built-in |