From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, aditya desai <admad123(at)gmail(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:43:36 |
Message-ID: | 20210403154336.GG29125@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-performance |
On Sat, Apr 3, 2021 at 10:41:14AM -0500, Justin Pryzby wrote:
> On Sat, Apr 03, 2021 at 11:39:19AM -0400, Tom Lane wrote:
> > 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.
>
> Because it's there to help DBAs catch errors in functions incorrectly marked as
> parallel safe.
Uh, isn't that developer/debugging?
--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EDB https://enterprisedb.com
If only the physical world exists, free will is an illusion.
From | Date | Subject | |
---|---|---|---|
Next Message | aditya desai | 2021-04-03 15:44:33 | Re: SELECT Query taking 200 ms on PostgreSQL compared to 4 ms on Oracle after migration. |
Previous Message | Bruce Momjian | 2021-04-03 15:42:59 | Re: SELECT Query taking 200 ms on PostgreSQL compared to 4 ms on Oracle after migration. |
From | Date | Subject | |
---|---|---|---|
Next Message | aditya desai | 2021-04-03 15:44:33 | Re: SELECT Query taking 200 ms on PostgreSQL compared to 4 ms on Oracle after migration. |
Previous Message | Bruce Momjian | 2021-04-03 15:42:59 | Re: SELECT Query taking 200 ms on PostgreSQL compared to 4 ms on Oracle after migration. |