| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | pgsql-committers(at)lists(dot)postgresql(dot)org |
| Subject: | pgsql: Limit to_tsvector_byid's initial array allocation to something s |
| Date: | 2023-09-25 15:50:43 |
| Message-ID: | E1qknr8-005tDD-Kl@gemulon.postgresql.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
Limit to_tsvector_byid's initial array allocation to something sane.
The initial estimate of the number of distinct ParsedWords is just
that: an estimate. Don't let it exceed what palloc is willing to
allocate. If in fact we need more entries, we'll eventually fail
trying to enlarge the array. But if we don't, this allows success on
inputs that currently draw "invalid memory alloc request size".
Per bug #18080 from Uwe Binder. Back-patch to all supported branches.
Discussion: https://postgr.es/m/18080-d5c5e58fef8c99b7@postgresql.org
Branch
------
REL_16_STABLE
Details
-------
https://git.postgresql.org/pg/commitdiff/8465efc1a0e721a070221c4aa83695422922b620
Modified Files
--------------
src/backend/tsearch/to_tsany.c | 2 ++
1 file changed, 2 insertions(+)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2023-09-25 16:07:35 | pgsql: Pack struct ParsedWord more tightly. |
| Previous Message | Tom Lane | 2023-09-25 15:50:42 | pgsql: Limit to_tsvector_byid's initial array allocation to something s |