fre 2016-07-22 klockan 19:08 +1200 skrev Mark Kirkwood:
> On 22/07/16 13:07, Johan Fredriksson wrote:
> > And by the way, I have also tried to upgrade to Postgresql 9.4.8 (the
> > latest version in postgresl.org's own repository) without improvment.
> >
>
> Not sure what repo you are using, but
On 22/07/16 13:07, Johan Fredriksson wrote:
And by the way, I have also tried to upgrade to Postgresql 9.4.8 (the latest
version in postgresl.org's own repository) without improvment.
Not sure what repo you are using, but 9.5.3 and 9.6 Beta are the
*actual* latest versions. Now I'm not sure
And by the way, I have also tried to upgrade to Postgresql 9.4.8 (the latest
version in postgresl.org's own repository) without improvment.
/ Eskil
--
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
I can add that setting enable_nestloop = 0 cuts the runtime for this query down
to about 4 seconds.
Disabling nested loops globaly does however impacts performance of a lot of
other queries.
/ Eskil
--
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make
On Thu, Jul 21, 2016 at 3:29 PM, David G. Johnston
wrote:
> On Thu, Jul 21, 2016 at 2:24 PM, Claudio Freire
> wrote:
>>
>> That cross join doesn't look right. It has no join condition.
>
>
> That is that the definition of a "CROSS JOIN"...
>
>
On Thu, Jul 21, 2016 at 2:24 PM, Claudio Freire
wrote:
> That cross join doesn't look right. It has no join condition.
That is that the definition of a "CROSS JOIN"...
David J.
On Thu, Jul 21, 2016 at 11:48 AM, Johan Fredriksson wrote:
> EXPLAIN ANALYZE VERBOSE SELECT DISTINCT main.* FROM Users main CROSS
> JOIN ACL ACL_3 JOIN Principals Principals_1 ON ( Principals_1.id =
> main.id ) JOIN CachedGroupMembers CachedGroupMembers_2 ON
> (
> > > The rowcount estimates from 9.2 seem greatly different from the 8.4 plan.
> > > Did you remember to ANALYZE all the tables after migrating? Maybe there
> > > were some table-specific statistics targets that you forgot to transfer
> > > over? In any case, the 9.2 plan looks like
> > The rowcount estimates from 9.2 seem greatly different from the 8.4 plan.
> > Did you remember to ANALYZE all the tables after migrating? Maybe there
> > were some table-specific statistics targets that you forgot to transfer
> > over? In any case, the 9.2 plan looks like
> > I am just about to upgrade from PostgreSQL 8.4.20 to 9.2.15, but I'v run
> > into some huge performance issues.
>
> The rowcount estimates from 9.2 seem greatly different from the 8.4 plan.
> Did you remember to ANALYZE all the tables after migrating? Maybe there
> were some table-specific
>
> ...(BTW, I wonder why you are moving only to 9.2 and not something more
>> recent.)
>>
>
> Well, 9.2.15 is what comes bundled with RHEL 7, so I decided to go with
> that to avoid dependency issues. But I could install a more fresh version
> from scratch if that would solve my problem.
>
The rowcount estimates from 9.2 seem greatly different from the 8.4 plan.
Did you remember to ANALYZE all the tables after migrating? Maybe there
were some table-specific statistics targets that you forgot to transfer
over?
No, I did not. Honestly I though everything would be transfered with
Johan Fredriksson writes:
> I am just about to upgrade from PostgreSQL 8.4.20 to 9.2.15, but I'v run
> into some huge performance issues.
The rowcount estimates from 9.2 seem greatly different from the 8.4 plan.
Did you remember to ANALYZE all the tables after migrating? Maybe
Hello!
I am just about to upgrade from PostgreSQL 8.4.20 to 9.2.15, but I'v run
into some huge performance issues. Both databases are configured the
same way (shared_buffers = 2GB, temp_buffers = 32MB). I have increased
work_mem on the 9.2 from 4MB to 64MB, but to no avail.
Now, the query on
14 matches
Mail list logo