| From: | Guillaume Smet <guillaume(dot)smet(at)gmail(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Finlay Thompson <finlay(at)dragonfly(dot)co(dot)nz>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #6275: Horrible performance regression |
| Date: | 2011-10-31 15:18:17 |
| Message-ID: | CALt0+o-L+2ajCSbFQQ-68=aYj-hNkEGw0baE4p_nBOSFxyKoyA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Mon, Oct 31, 2011 at 1:50 PM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> If you can't do that for some reason, there's always auto_explain, but
> that has some overhead and is a bit more work to set up.
If it's a massive load of data with a lot of queries, I think his best
bet is to log the queries with log_min_duration_statement = <something
sensible> (I'd try to start with 30ms) then analyze the log results
with pgFouine or any other log analyzer for both versions.
--
Guillaume
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2011-10-31 16:13:40 | Re: BUG #6278: Index scans on '>' condition on field with many NULLS |
| Previous Message | Tom Lane | 2011-10-31 14:37:38 | Re: BUG #6278: Index scans on '>' condition on field with many NULLS |