| From: | Viktor Fougstedt <viktor(at)chalmers(dot)se> |
|---|---|
| To: | pinker <pinker(at)onet(dot)eu> |
| Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Query which "never" terminates |
| Date: | 2017-04-27 14:28:43 |
| Message-ID: | 0EF86AD6-AA51-4E2A-9A19-B3AC1E27A2F1@chalmers.se |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hello,
and thanks for your reply.
SET from_collapse_limit=1;
did no difference, I’m afraid.
I ran both VACUUM and ANALYZE before I posted, and there was no noticable difference from either of them.
Regards,
/Viktor
> On 27 apr 2017, at 15:54, pinker <pinker(at)onet(dot)eu> wrote:
>
> Try to change from_collapse_limit values at first, for instance run SET
> from_collapse_limit = 1; and then your query in the same session.
> have you ran analyze lately?
>
>
>
> --
> View this message in context: http://www.postgresql-archive.org/Query-which-never-terminates-tp5958734p5958736.html
> Sent from the PostgreSQL - general mailing list archive at Nabble.com.
>
>
> --
> Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniel Westermann | 2017-04-27 15:41:34 | PostgreSQL upgrade best practices, please share your thoughts |
| Previous Message | Jan de Visser | 2017-04-27 14:08:16 | Re: Postgres connection Monitor |