pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: PG Bug reporting form <noreply@postgresql.org>
To: pgsql-bugs@lists.postgresql.org
Cc: github@cquest.org
Subject: BUG #16183: PREPARED STATEMENT slowed down by jit
Date: Thu, 02 Jan 2020 10:48:17 +0000
Message-ID: <16183-64843a4ebc44d9d2@postgresql.org> (raw)

The following bug has been logged on the website:

Bug reference:      16183
Logged by:          Christian Quest
Email address:      github@cquest.org
PostgreSQL version: 12.1
Operating system:   Ubuntu 18.04
Description:        

I'm running several OpenStreetMap map rendering servers. They are all based
on PG/postgis.
After an upgrade from v10 to 12, the usual update process took 10x more time
than it used to.

After digging a few days, it appear that the default jit=on is the cause.

The update tool (osm2pgsql) makes heavy use of PREPARED statements. Could
there be a bug in jit+PREPARED causing the statement to be recompiled on
each execute ?

The other side of the issue is described here:
https://github.com/openstreetmap/osm2pgsql/issues/1045



view thread (9+ messages)  latest in thread

Message-ID: <16183-64843a4ebc44d9d2@postgresql.org>
Permalink:  ../16183-64843a4ebc44d9d2@postgresql.org/
Also on:    postgresql.org/message-id/16183-64843a4ebc44d9d2@postgresql.org

 · 

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: noreply@postgresql.org, github@cquest.org
  Subject: Re: BUG #16183: PREPARED STATEMENT slowed down by jit
  In-Reply-To: <16183-64843a4ebc44d9d2@postgresql.org>
  References: <16183-64843a4ebc44d9d2@postgresql.org>

* 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