| From: | Robert Creager <robert(at)logicalchaos(dot)org> |
|---|---|
| To: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
| Cc: | pgsql-general(at)postgresql(dot)org, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Subject: | Re: Query hitting empty tables taking 48 minutes |
| Date: | 2018-06-19 00:28:03 |
| Message-ID: | 4457A071-1CE2-4936-BFD5-D93F629FF7AF@logicalchaos.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> On Jun 18, 2018, at 4:33 PM, Robert Creager <robert(at)logicalchaos(dot)org> wrote:
>
>> I cannot explain the discrepancy between the runtimes of 85 seconds versus 10857 seconds.
>
> It would be nice if the auto_explain analyze did include the other information like the psql analyze does.
Like this. I’ll try again.
auto_explain.log_triggers (boolean)
auto_explain.log_triggers causes trigger execution statistics to be included when an execution plan is logged. This parameter has no effect unless auto_explain.log_analyze is enabled. This parameter is off by default. Only superusers can change this setting.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Benjamin Scherrey | 2018-06-19 03:15:52 | Re: High WriteLatency RDS Postgres 9.3.20 |
| Previous Message | Sherrylyn Branchaw | 2018-06-18 23:50:04 | Re: What to do when dynamic shared memory control segment is corrupt |