From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
---|---|
To: | Simon Windsor <simon(dot)windsor(at)cornfield(dot)me(dot)uk>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Slow timestamp query after upgrading from Pg13 to Pg16 |
Date: | 2025-04-08 06:40:11 |
Message-ID: | 53f4c3238460ea2b6e8677b4419bacd6a4445e83.camel@cybertec.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Mon, 2025-04-07 at 20:25 +0100, Simon Windsor wrote:
> We used pg_dump|pg_restore to migrate the data.
>
> The full explain plan is at https://explain.depesz.com/s/742M. The SQL
>
> explain (analyze, buffers) select count(*) from consignments where
> (req_status_tstamp >= '2025-03-28 00:00'::timestamp and
> req_status_tstamp <= '2025-03-28 01:00'::timestamp);
>
> takes 2-3s with the old Pg13 DB, and over a minute with Pg16
>
> After spending many hours looking at DB settings and Statistic settings
> I am at a loss/
Thanks.
- Can you show the index definitions on that table?
- If you "SET enable_seqscan = off;" in an interactive session, PostgreSQL
should choose an index scan if possible. Can you show the
EXPLAIN (ANALYZE, BUFFERS) output for that execution?
Yours,
Laurenz Albe
From | Date | Subject | |
---|---|---|---|
Next Message | yudhi s | 2025-04-08 10:38:22 | Queries for monitor |
Previous Message | Laurenz Albe | 2025-04-08 05:53:09 | Re: find replication slots that "belong" to a publication |