| From: | "John Watts" <jwatts(at)promotion-update(dot)com> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "John Watts" <jwatts(at)promotion-update(dot)com> |
| Cc: | <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: difference in query plan when db is restored |
| Date: | 2012-05-17 21:20:30 |
| Message-ID: | 3CCE373A5F700D4AA37233BADC93F04C030DCA@bgva-s03-exch03.taxback.ess.ie |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
No change I'm afraid :(
-----Original Message-----
From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]
Sent: 17 May 2012 22:59
To: John Watts
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: [GENERAL] difference in query plan when db is restored
"John Watts" <jwatts(at)promotion-update(dot)com> writes:
> I have a database query which executes normal (under 1s) with 21 steps
> according to the query paln. However, when the database is dumped and
> restored on the _same_ PostgreSQL server, the query plan takes 34
> steps to complete and it executes in excess of 90 seconds!
Usually you need to ANALYZE after restoring from a dump ...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Clemens Eisserer | 2012-05-17 22:44:41 | Reasons for postgres processes beeing killed by SIGNAL 9? |
| Previous Message | Tom Lane | 2012-05-17 19:58:32 | Re: difference in query plan when db is restored |