| From: | Andrei Lepikhov <lepihov(at)gmail(dot)com> |
|---|---|
| To: | FREYBURGER Simon "(SNCF" VOYAGEURS / DIRECTION GENERALE TGV / DM RMP YIELD "MANAGEMENT)" <simon(dot)freyburger(at)sncf(dot)fr>, "pgsql-performance(at)lists(dot)postgresql(dot)org" <pgsql-performance(at)lists(dot)postgresql(dot)org>, Peter Geoghegan <pg(at)bowt(dot)ie> |
| Subject: | Re: How to solve my slow disk i/o throughput during index scan |
| Date: | 2024-07-11 15:22:09 |
| Message-ID: | 6bf23d96-4920-4bf1-9c08-96d544f505ad@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On 11/7/2024 22:09, FREYBURGER Simon (SNCF VOYAGEURS / DIRECTION
GENERALE TGV / DM RMP YIELD MANAGEMENT) wrote:
> Is it possible to parallelize the scans during the modify step ?
Temporary tables can't be used inside a query with parallel workers
involved, because such table is local for single process.
What about your question - I'm not sure without whole bunch of data. But
maximum speedup you can get by disabling as much constraints as possible
- ideally, fill each partition individually with no constraints and
indexes at all before uniting them into one partitioned table.
--
regards, Andrei Lepikhov
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrei Lepikhov | 2024-07-11 15:34:54 | Re: How to solve my slow disk i/o throughput during index scan |
| Previous Message | David G. Johnston | 2024-07-11 15:19:51 | Re: How to solve my slow disk i/o throughput during index scan |