pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Christian Schwaderer <schwaderer@ivocotec.de>
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #16223: Performance regression between 11.6 and 12.1 in an SQL query with a recursive CTE based on function
Date: Mon, 27 Jan 2020 10:31:44 -0500
Message-ID: <3381.1580139104@sss.pgh.pa.us> (raw)
In-Reply-To: <961e4c0f-bdd4-4733-4706-0b19d8a8559f@ivocotec.de>
References: <16223-908afaa0eaf46ea2@postgresql.org>
	<47fea63b-fb4a-251d-8cff-a1b67161f039@ivocotec.de>
	<670FCE85-3229-40B0-A211-0599B88B611F@yesql.se>
	<961e4c0f-bdd4-4733-4706-0b19d8a8559f@ivocotec.de>

Christian Schwaderer <schwaderer@ivocotec.de> writes:
> I only tested on those virtual environments mentioned (Virtual Box and 
> Docker) as they resemble my real life scenarios. Environments were 
> equivalent except for the PostgreSQL version. As you can see, I used 
> Docker images from the official PostgreSQL docker repo ( 
> https://hub.docker.com/_/postgres ) and did nothing with them except 
> running the query.

> Thanks for testing without virtualization! So, it seems we can narrow 
> down the issue to virtual environments. Strange enough, if you ask me.

Or it could be the specific builds you used.  Some of our packagers
tend to enable debug options on early releases of a given major version;
if that was the case for the v12 build you tested, it could account for
at least some of the difference.  Comparing pg_config output from the
two installations (particularly the configure options) would be
informative.

Another thing that could be relevant is JIT, which is on by default
in v12 (if enabled in configuration), and which is still suffering
a lot of teething pains performance-wise.  I'd check if that's
on and try disabling it if so.

			regards, tom lane





view thread (9+ messages)  latest in thread

Message-ID: <3381.1580139104@sss.pgh.pa.us>
Permalink:  ../3381.1580139104@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/3381.1580139104@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-bugs@postgresql.org
  Cc: tgl@sss.pgh.pa.us, schwaderer@ivocotec.de
  Subject: Re: BUG #16223: Performance regression between 11.6 and 12.1 in an SQL query with a recursive CTE based on function
  In-Reply-To: <3381.1580139104@sss.pgh.pa.us>
  References: <16223-908afaa0eaf46ea2@postgresql.org> <47fea63b-fb4a-251d-8cff-a1b67161f039@ivocotec.de> <670FCE85-3229-40B0-A211-0599B88B611F@yesql.se> <961e4c0f-bdd4-4733-4706-0b19d8a8559f@ivocotec.de> <3381.1580139104@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox