pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Andres Freund <andres@anarazel.de>
To: Thomas Butz <tbutz@optitool.de>
Cc: pgsql-bugs <pgsql-bugs@lists.postgresql.org>
Subject: Re: BUG #16241: Degraded hash join performance
Date: Tue, 4 Feb 2020 07:01:52 -0800
Message-ID: <20200204150152.prebesyfo2idnyum@alap3.anarazel.de> (raw)
In-Reply-To: <87490169.275301.1580827750088.JavaMail.zimbra@optitool.de>
References: <20200204134408.oing4ypvshgr5ykx@alap3.anarazel.de>
	<87490169.275301.1580827750088.JavaMail.zimbra@optitool.de>

Hi,

On 2020-02-04 15:49:10 +0100, Thomas Butz wrote:
> I was able to reduce it to a minimal example:
> 
> SELECT localized_streetname
> FROM planet_osm_line
> WHERE "way" && ST_SetSRID('BOX3D(1222380.956336539 6339381.37785938,1233387.888409604 6350388.309932444)'::box3d, 3857)
> 
> Your diagnosis with osml10n_get_streetname_from_tags was spot on. I'm going to report it to the author of the osml10n extension.

Cool. Still worth checking whether there's a 11 vs 12 issue inside that function.



> Thank you for your help!
> 
> PS: I've created the execution plans using EXPLAIN (ANALYZE, VERBOSE, COSTS, BUFFERS, TIMING, SUMMARY, FORMAT json) but i wasn't aware that i might have to check the "Output" section of a node to find potential performance problems. How do you find such slow outputs without using perf?

It's not trivial, unfortunately :(. You can use track_functions to get
more insight, but that's better for server-wide analysis, than query
specific ones.  auto_explain also has options to track nested queries,
which might help as well.

I hope we can extend EXPLAIN with more information about this kind of
thing at some point.

Regards,

Andres





view thread (9+ messages)  latest in thread

Message-ID: <20200204150152.prebesyfo2idnyum@alap3.anarazel.de>
Permalink:  ../20200204150152.prebesyfo2idnyum@alap3.anarazel.de/
Also on:    postgresql.org/message-id/20200204150152.prebesyfo2idnyum@alap3.anarazel.de

 · 

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: andres@anarazel.de, tbutz@optitool.de
  Subject: Re: BUG #16241: Degraded hash join performance
  In-Reply-To: <20200204150152.prebesyfo2idnyum@alap3.anarazel.de>
  References: <20200204134408.oing4ypvshgr5ykx@alap3.anarazel.de> <87490169.275301.1580827750088.JavaMail.zimbra@optitool.de> <20200204150152.prebesyfo2idnyum@alap3.anarazel.de>

* 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