| From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | Yevhenii Kurtov <yevhenii(dot)kurtov(at)gmail(dot)com> |
| Cc: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: |
| Date: | 2017-06-30 03:09:28 |
| Message-ID: | CAOR=d=1oVjzX6Psy_x5aCcvskvSvD-9R4+FNSgWGjf_67Wu8oA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Thu, Jun 29, 2017 at 1:11 PM, Yevhenii Kurtov
<yevhenii(dot)kurtov(at)gmail(dot)com> wrote:
> Hi Jeff,
>
> That is just a sample data, we are going live in Jun and I don't have
> anything real so far. Right now it's 9.6 and it will be a latest stable
> available release on the date that we go live.
Trust me on this one, you want to get some realistic fake data in
there, and in realistic quantities before you go live to test.
Postgresql's planner makes decisions based on size of the data it has
to trundle through and statistical analysis of the data in the tables
etc. You don't wanna go from 500 rows in a test table with the same
values to 10,000,000 rows with wildly varying data in production
without having some clue where that db is gonna be headed performance
wise.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Janes | 2017-06-30 17:46:45 | Re: |
| Previous Message | Alvaro Herrera | 2017-06-29 21:28:23 | Re: |