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@heroku.com>
>On Sat, Jan 16, 2016 at 4:51 AM, Master ZX <zx-master@bigmir.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
firstorder.
> > 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
