Re: [GENERAL] Postgres 9.6.1 big slowdown by upgrading 8.4.22

2017-01-08 Thread Chris Mair
I would also like to add this: The explain analyze show that the index on that numeric field *is not* being used. I also try to set the seqscan off but that index continues not to be used. Maybe the problem is this? Thank you again! /F Hi, maybe I missed something, but it appears to me you

Re: [GENERAL] Postgres 9.6.1 big slowdown by upgrading 8.4.22

2017-01-07 Thread Tom Lane
Tomas Vondra writes: > No. now() calls GetCurrentTransactionStartTimestamp(), so it does not > call gettimeofday() and so the clock source overhead is pretty much > irrelevant. Moreover it's marked as 'stable' which makes repeated calls > unnecessary. Yeah. My own thought, in view of the larg

Re: [GENERAL] Postgres 9.6.1 big slowdown by upgrading 8.4.22

2017-01-07 Thread Tomas Vondra
On 01/08/2017 01:12 AM, Alban Hertroys wrote: On 7 Jan 2017, at 15:44, Job wrote: ... This is what it happens: Postgres 8.4.22 Medium average load 1.5/2.0 Further queries respond very quickly Postgres 9.6.1 Medium average load 18.0/20.0 !! Further queries are really very slow There is a bo

Re: [GENERAL] Postgres 9.6.1 big slowdown by upgrading 8.4.22

2017-01-07 Thread Alban Hertroys
> On 7 Jan 2017, at 15:44, Job wrote: > > Hi guys, > > First of all excuse me but i really do not explain the problem, sorry... > >>> Are you being serious? You're complaining about a "big slowdown" for a >>> query that goes from 1.5ms to 4ms? >>> What is the actual problem you're trying to s

Re: [GENERAL] Postgres 9.6.1 big slowdown by upgrading 8.4.22

2017-01-07 Thread Tomas Vondra
On 01/07/2017 04:43 AM, Venkata B Nagothi wrote: On Sat, Jan 7, 2017 at 2:56 AM, Job > wrote: __ Hi guys, really much appreciated your replies. >> You might want to include the query plans for each server W e use a function, the explain

Re: [GENERAL] Postgres 9.6.1 big slowdown by upgrading 8.4.22

2017-01-06 Thread Venkata B Nagothi
On Sat, Jan 7, 2017 at 2:56 AM, Job wrote: > Hi guys, > > really much appreciated your replies. > > >> You might want to include the query plans for each server > > W e use a function, the explain analyze is quite similar: > POSTGRESQL 8.4.22: > > explain analyze select 'record.com' where 'recor

Re: [GENERAL] Postgres 9.6.1 big slowdown by upgrading 8.4.22

2017-01-06 Thread Melvin Davidson
On Fri, Jan 6, 2017 at 4:56 PM, Alban Hertroys wrote: > > > On 6 Jan 2017, at 16:56, Job wrote: > > > > W e use a function, the explain analyze is quite similar: > > POSTGRESQL 8.4.22: > > Total runtime: 1.531 ms > > > > POSTGRES 9.6.1: > > Execution time: 4.230 ms > > Are you being serious? Y

Re: [GENERAL] Postgres 9.6.1 big slowdown by upgrading 8.4.22

2017-01-06 Thread Alban Hertroys
> On 6 Jan 2017, at 16:56, Job wrote: > > W e use a function, the explain analyze is quite similar: > POSTGRESQL 8.4.22: > Total runtime: 1.531 ms > > POSTGRES 9.6.1: > Execution time: 4.230 ms Are you being serious? You're complaining about a "big slowdown" for a query that goes from 1.5m

Re: [GENERAL] Postgres 9.6.1 big slowdown by upgrading 8.4.22

2017-01-05 Thread Tom Lane
Job writes: > Could you please help me? There's advice here on how to ask this type of question with enough detail to get answers: https://wiki.postgresql.org/wiki/Slow_Query_Questions regards, tom lane -- Sent via pgsql-general mailing list (pgsql-general@postgresql.

Re: [GENERAL] Postgres 9.6.1 big slowdown by upgrading 8.4.22

2017-01-05 Thread Rob Sargent
On 01/05/2017 10:18 AM, Job wrote: Hello guys, a very strange thing: after upgrading from 8.4.22 to 9.6.1 i noticed, under heavy beanchmarks, a really slowdown of Postgresql 9.6.1, with the machine really "without breath". By replacing Postgresql 8.4.22 evberything returns working fine. With