> Hi Eskil -
>
>
> The I believe the id-field you're referring to is the UNIT.UNIT_ID, I
> could change this to a varchar, however that column is not used in the
> query in question, so that wouldn't have any effect on the query's
> performance.
Sorry, I did not notice that the column "unit_id
tis 2017-04-25 klockan 23:19 -0400 skrev Alessandro Ferrucci:
> After about 40 inutes the slow query finally finished and the result
> of the EXPLAIN plan can be found here:
>
>
> https://explain.depesz.com/s/BX22
>
>
> Thanks,
> Alessandro Ferrucci
I'm not so familiar with the index implement
> Sir/Madam,
> Plateform: RHEL6.5, Postgresql9.4.0.
>
>
> create extension plperl;
>
> Create language plperl;
>
>
> I have done following settings:
>
> Perl version 5.10
> vi /etc/ld.so.conf.d/libperl.conf
> /usr/lib/5.10/multi-thread/i386.../CORE/libperl.so
> ldconfig
>
>
> ERROR: Can n
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 s
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:
http://www.postgresql.o
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
> > > 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 garbage-in-g
> > 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 garbage-in-garbage-o
> > 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 st
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 a
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 8.4:
11 matches
Mail list logo