From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Guyren Howe <guyren(at)gmail(dot)com> |
Cc: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Reproducing query plans in empty database: can I just copy stats and settings? |
Date: | 2019-07-29 22:08:06 |
Message-ID: | 21596.1564438086@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Guyren Howe <guyren(at)gmail(dot)com> writes:
> On Jul 29, 2019, at 12:25 , Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> wrote:
>> If you can't see/use the data in the production database in your test database I'm not sure how copying the statistics/cost settings is going to help.
> Isn’t that the entirety of what the query plan is based on?
No; physical sizes of the tables and indexes also matter. (The planner
scales some cost values by those numbers to account for the likelihood
that tables have grown since they were last analyzed.) You could deal
with that by bloating them with dummy data, of course.
I think though that Adrian's point is a bit different: if you're not
allowed to see the original data, you should not be allowed to see
the statistics either. The histogram values and most-common-values
lists represent a pretty sizable information leak for such cases.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2019-07-29 23:04:21 | Re: Reproducing query plans in empty database: can I just copy stats and settings? |
Previous Message | Guyren Howe | 2019-07-29 21:59:08 | Re: Reproducing query plans in empty database: can I just copy stats and settings? |