| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | aditya desai <admad123(at)gmail(dot)com>, Justin Pryzby <pryzby(at)telsasoft(dot)com>, Pgsql Performance <pgsql-performance(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: SELECT Query taking 200 ms on PostgreSQL compared to 4 ms on Oracle after migration. |
| Date: | 2021-04-03 15:39:19 |
| Message-ID: | 3972636.1617464359@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-performance |
Bruce Momjian <bruce(at)momjian(dot)us> writes:
> On Sat, Apr 3, 2021 at 08:38:18PM +0530, aditya desai wrote:
>> Yes, force_parallel_mode is on. Should we set it off?
> Yes. I bet someone set it without reading our docs:
> https://www.postgresql.org/docs/13/runtime-config-query.html#RUNTIME-CONFIG-QUERY-OTHER
> --> Allows the use of parallel queries for testing purposes even in cases
> --> where no performance benefit is expected.
> We might need to clarify this sentence to be clearer it is _only_ for
> testing.
I wonder why it is listed under planner options at all, and not under
developer options.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Justin Pryzby | 2021-04-03 15:41:14 | Re: SELECT Query taking 200 ms on PostgreSQL compared to 4 ms on Oracle after migration. |
| Previous Message | Bruce Momjian | 2021-04-03 15:38:12 | Re: SELECT Query taking 200 ms on PostgreSQL compared to 4 ms on Oracle after migration. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Justin Pryzby | 2021-04-03 15:41:14 | Re: SELECT Query taking 200 ms on PostgreSQL compared to 4 ms on Oracle after migration. |
| Previous Message | Bruce Momjian | 2021-04-03 15:38:12 | Re: SELECT Query taking 200 ms on PostgreSQL compared to 4 ms on Oracle after migration. |