| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Kostas Papadopoulos <kostas(at)methodosit(dot)com(dot)cy> |
| Cc: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Daevor The Devoted <dollien(at)gmail(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org, Julien Rouhaud <rjuju123(at)gmail(dot)com> |
| Subject: | Re: Same query, same data different plan |
| Date: | 2022-10-10 14:53:43 |
| Message-ID: | 4073393.1665413623@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Kostas Papadopoulos <kostas(at)methodosit(dot)com(dot)cy> writes:
> I cannot see how it can be configuration since the two databases are in the same
> Postgres instance.
There is such a thing as ALTER DATABASE ... SET to install different
settings at the per-database level.
In general, the answer to your question is that the databases are
*not* identical. You just haven't figured out how yet. I'm wondering
if it has something to do with the dump/reload having compacted out
bloat in the tables or indexes, causing cost estimates to change.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kostas Papadopoulos | 2022-10-10 15:12:11 | Re: Same query, same data different plan |
| Previous Message | Adrian Klaver | 2022-10-10 14:26:02 | Re: Same query, same data different plan |