Re: R: R: Postgres 9.6.1 big slowdown by upgrading 8.4.22

From: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
To: Job <Job(at)colliniconsulting(dot)it>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: R: R: Postgres 9.6.1 big slowdown by upgrading 8.4.22
Date: 2017-01-09 16:26:04
Message-ID: 67938507-1ae4-3bc3-fba0-be4a56ea5bd0@aklaver.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 01/09/2017 01:33 AM, Job wrote:
> Hi guys,
>
> Really thank you.
> Thanks to your help i solved the problem.

For the record which problem(s)?:

1) Your original function issue.

2) The stand alone query you showed later.

3) Both.

>
> As said by Adrian:
>
>>> Caveats, it is morning here and coffee is still brewing, but I am not following. The left join limits grulist.stato to NULL, 1, 2. Your first condition catches the 1 value. Should not the second 'and' be (stato = 2 or stato is >>
>>> null). In fact I do not see why it needs to exist at all, which seems to be borne out by your experimentation.
>
> O doubled conditions, without reason!
>
> I think making good queries is an art, at the moment i am not an artist! :)
>
> Again,thank you very much!
>
> /F
>
>
>

--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Edmundo Robles 2017-01-09 16:45:57 Why autvacuum is not started?
Previous Message Adrian Klaver 2017-01-09 15:37:40 Re: checkpoint clarifications needed