| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Maxim Boguk <maxim(dot)boguk(at)gmail(dot)com> |
| Cc: | David Rowley <dgrowleyml(at)gmail(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #18588: Cannot force/let database use parallel execution in simple case. |
| Date: | 2024-08-22 20:52:43 |
| Message-ID: | 2074136.1724359963@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Maxim Boguk <maxim(dot)boguk(at)gmail(dot)com> writes:
> With sufficiently large table - I didn't manage find a combinations of
> settings to force parallel execution (im my real case - the database huge
> and mostly cold on ssd raid - so parallel execution provides almost linear
> speedup with amount of parallel workers even on 1000 rows... not talking
> about 10k-10m rows, but I cannot convince the PostgreSQL use parallel index
> scan for 2m returned rows case).
Well, there may be something going on in your real case that isn't
apparent from this toy example. Perhaps look for a better example?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Maxim Boguk | 2024-08-22 21:16:17 | Re: BUG #18588: Cannot force/let database use parallel execution in simple case. |
| Previous Message | Tom Lane | 2024-08-22 20:42:03 | Re: BUG #18588: Cannot force/let database use parallel execution in simple case. |