| From: | "Jonah H(dot) Harris" <jonah(dot)harris(at)gmail(dot)com> |
|---|---|
| To: | don(at)seiler(dot)us |
| Cc: | Markus(dot)Zwettler(at)zuerich(dot)ch, srinivasoguri7(at)gmail(dot)com, pgsql-admin(at)lists(dot)postgresql(dot)org |
| Subject: | Re: query performance after database rename |
| Date: | 2018-11-21 16:06:59 |
| Message-ID: | CADUqk8VYvMc8ZvW=V41qzGA2SpCJxufPx+sYpQ+qKD4X0ErNYw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Wed, Nov 21, 2018 at 9:54 AM Don Seiler <don(at)seiler(dot)us> wrote:
> Off the top of my head, I'd say after switching to a new database, you'd
> have a cold buffer cache. There's a possibility of old statistics. Are you
> syncing data changes from the old DB to the new DB?
>
Yeah. That would be my guess as well. Sounds like blocks from the new
database would likely be causing high evictions from those of the old
database. Would be interesting to see an overview of it with pg_buffercache.
Also, I'm curious *why* you're doing this.
>
Ditto.
--
Jonah H. Harris
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Maycon Oleczinski | 2018-11-22 11:52:56 | pgAdmin 4 v3.5 eternal loading |
| Previous Message | Zwettler Markus (OIZ) | 2018-11-21 15:41:59 | AW: query performance after database rename |