pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Lowell Hought <lowell.hought@gmail.com>
Cc: Laurenz Albe <laurenz.albe@cybertec.at>
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18950: pgsql function that worked in Postgresql 16 does not return in Postgresql 17
Date: Sat, 14 Jun 2025 18:26:37 -0400
Message-ID: <49486.1749939997@sss.pgh.pa.us> (raw)
In-Reply-To: <CAJtAGPrZwQZW5idX6p_y7Fm+37TxBg=HkBcGQhCt6MjvTXmnkw@mail.gmail.com>
References: <e9eb5136fb60188fc61c110e9706709fc13638e0.camel@cybertec.at>
	<75D714EA-CD1E-4F80-A2E8-29E378EC2200@gmail.com>
	<81946.1749348479@sss.pgh.pa.us>
	<CAJtAGPpa4yYS6LLO5RHzwe9q7NpHiuuvEX1wVtErpie3EBWZJQ@mail.gmail.com>
	<CAJtAGPrcK_gp8FuEzp4tTbLKD1mqFGY5yDk0FX_1AGDjVJXAuw@mail.gmail.com>
	<CAJtAGPpeqrgKNHdWqr=uPu1_UwN_TAgUvN4cfcWOaRN8U+8zDA@mail.gmail.com>
	<89144.1749352271@sss.pgh.pa.us>
	<CAJtAGPpURGxCJRWVeFsPbu2fjtaSCwVsBNZ5_QW0wE5N6Z-N=Q@mail.gmail.com>
	<90964.1749353175@sss.pgh.pa.us>
	<CAJtAGPof_SZ4mWHwv5QJqu43NzmO7EVCW_Rc-EDX8qKemCsyhw@mail.gmail.com>
	<CAJtAGPrmPgyLZfL2TL5oN8iN2yzz0=r98twiHWrWxos0ytmGtA@mail.gmail.com>
	<1628600.1749914148@sss.pgh.pa.us>
	<CAJtAGPriJrVYmWKyPaMhmHCnLqA4Rs7tv2=r_zZ2sTpg_Z-ZNw@mail.gmail.com>
	<1634855.1749917537@sss.pgh.pa.us>
	<CAJtAGPrZwQZW5idX6p_y7Fm+37TxBg=HkBcGQhCt6MjvTXmnkw@mail.gmail.com>

Lowell Hought <lowell.hought@gmail.com> writes:
> Attached in three separate files.

Thanks.  The only thing that's really obvious here is that the
rowcount estimates must be way off, because if the join outputs
were as small as the planner thinks, this query couldn't take
very long at all.  I wonder whether your v17 installation is
lacking appropriate statistics.  By now autovacuum should have
mostly filled that in even if you forgot to see to it when
transferring data --- but maybe you had larger-than-default
statistics targets in the v16 installation?  Or some other
change to the default settings?  I'd double-check that and
then do a manual ANALYZE of the whole database, and see if
anything changes.

			regards, tom lane





view thread (20+ messages)

Message-ID: <49486.1749939997@sss.pgh.pa.us>
Permalink:  ../49486.1749939997@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/49486.1749939997@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 using the --to and --cc options:
  reply via email

  To: pgsql-bugs@postgresql.org
  Cc: tgl@sss.pgh.pa.us, lowell.hought@gmail.com, laurenz.albe@cybertec.at, pgsql-bugs@lists.postgresql.org
  Subject: Re: BUG #18950: pgsql function that worked in Postgresql 16 does not return in Postgresql 17
  In-Reply-To: <49486.1749939997@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