| From: | Alexander Pyhalov <a(dot)pyhalov(at)postgrespro(dot)ru> |
|---|---|
| To: | Tomas Vondra <tomas(at)vondra(dot)me> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Limit memory usage by postgres_fdw batches |
| Date: | 2026-02-10 13:31:12 |
| Message-ID: | f3f1c9f2688c00e5d6a390484b75ee2b@postgrespro.ru |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi.
Attaching new version of patches. Besides some bit-size fixes, last
series of patches managed to limit MOVE operations. Fixed this.
--
Best regards,
Alexander Pyhalov,
Postgres Professional
| Attachment | Content-Type | Size |
|---|---|---|
| v6-0001-Introduce-function-to-estimate-tuple-size.patch | text/x-diff | 3.0 KB |
| v6-0002-Limit-batch_size-for-foreign-insert-with-work_mem.patch | text/x-diff | 11.1 KB |
| v6-0003-Introduce-memory-limited-cursors-and-use-them-in-pos.patch | text/x-diff | 32.2 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | John Naylor | 2026-02-10 13:37:59 | Re: tuple radix sort |
| Previous Message | Nitin Motiani | 2026-02-10 13:09:18 | Re: [PATCH] Support reading large objects with pg_read_all_data |