From: | Master ZX <zx-master(at)bigmir(dot)net> |
---|---|
To: | pgsql-bugs(at)postgresql(dot)org <pgsql-bugs(at)postgresql(dot)org> |
Subject: | Re[2]: [BUGS] Re[2]: [BUGS] BUG #13869: Right Join query that never ends |
Date: | 2016-02-11 17:34:55 |
Message-ID: | E1aTv8p-0007DN-Sz@bst04.sputnikmedia.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
In new release 9.5.1 this bug is no longer exists.
This issue should be closed.
19.01.2016 02:47, Peter Geoghegan <pg(at)heroku(dot)com>
>On Sat, Jan 16, 2016 at 4:51 AM, Master ZX <zx-master(at)bigmir(dot)net> wrote:
> > I can do more to investigate this behavior only if postgresql will consider my claim as bug that has to be fixed in first order.
> > Ideally I should give my DB schema and dump or VM wich reproduces this bug, but I can not give away our internal data. All other options I can not describe at public mailing list.
>
> Why don't you use a tool like Linux's perf to determine where time is spent?:
>
> https://wiki.postgresql.org/wiki/Profiling_with_perf
>
> A simple "perf top" may be all that it takes to give us a better idea
> of where time is spent.
>
> --
> Peter Geoghegan
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2016-02-11 19:35:52 | Re: SQL parser ubnormal behaviour |
Previous Message | Alexey Makhmutov | 2016-02-11 16:35:48 | Re[2]: [BUGS] BUG #13935: Duplicate row in pg_constraint table which is not accessible via indexes |