On 10/29/2015 11:24 AM, Tom Lane wrote:
> Matthew Bellew writes:
>> I made have several users encounter performance problems, which all
>> seem to come down to this problem: multiplying selectivity estimates can
>> cause tuple estimates to grow very small very quickly, once the estimator
>> gets t
Matthew Bellew writes:
> I made have several users encounter performance problems, which all
> seem to come down to this problem: multiplying selectivity estimates can
> cause tuple estimates to grow very small very quickly, once the estimator
> gets to 1 row, the planner may choose plans that are
This related to a post in the general bugs forum, but I found this forum,
and
this seems more appropriate. This is my second attempt to post, I believe
the first attempt last week did not work, apologies if I'm duplicating.
http://comments.gmane.org/gmane.comp.db.postgresql.bugs/39011
I made ha
On 28.10.2015 8:04, Javier Muro wrote:
Has PostgreSQL 9.4 official Support on a system with more than 64
legitimate cores? ( 72 Cores , 4 CPUs Intel(R) Xeon(R) CPU E7-8890 )
The work Robert Haas did to fix the CPU locking way back when showed
significant improvements up to 64, but so far a
Yes, the three fields index AND vacuum solve the issue.
Regards,
Bertrand
2015-10-29 13:27 GMT+01:00 Alex Ignatov :
>
>
> On 27.10.2015 23:56, Bertrand Paquet wrote:
>
> So,
>
> Tonight, the index on the three field is used, may be my yesterday vacuum
> updated stats.
>
> Thx you for your help.
On 27.10.2015 23:56, Bertrand Paquet wrote:
So,
Tonight, the index on the three field is used, may be my yesterday
vacuum updated stats.
Thx you for your help.
Regards,
Bertrand
2015-10-27 18:33 GMT+01:00 Bertrand Paquet
mailto:bertrand.paq...@doctolib.fr>>:
Hi tom,
I did
