Re: SELECT Query taking 200 ms on PostgreSQL compared to 4 ms on Oracle after migration. - Mailing list pgsql-performance

From Tom Lane
Subject Re: SELECT Query taking 200 ms on PostgreSQL compared to 4 ms on Oracle after migration.
Date
Msg-id 3972636.1617464359@sss.pgh.pa.us
Whole thread Raw
In response to Re: SELECT Query taking 200 ms on PostgreSQL compared to 4 ms on Oracle after migration.  (Bruce Momjian <bruce@momjian.us>)
Responses Re: SELECT Query taking 200 ms on PostgreSQL compared to 4 ms on Oracle after migration.
Re: SELECT Query taking 200 ms on PostgreSQL compared to 4 ms on Oracle after migration.
List pgsql-performance
Bruce Momjian <bruce@momjian.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



pgsql-performance by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: SELECT Query taking 200 ms on PostgreSQL compared to 4 ms on Oracle after migration.
Next
From: Justin Pryzby
Date:
Subject: Re: SELECT Query taking 200 ms on PostgreSQL compared to 4 ms on Oracle after migration.