Re: Statistics Injection - Mailing list pgsql-hackers

From Victor Giannakouris - Salalidis
Subject Re: Statistics Injection
Date
Msg-id CALUSaSpUz6962i0Dob66k_Q=58wcYvKiWxORLG0ay_cG=-KUmA@mail.gmail.com
Whole thread Raw
In response to Re: Statistics Injection  (Vladimir Sitnikov <sitnikov.vladimir@gmail.com>)
List pgsql-hackers
Hello,

pg_dbms_stats worked well for my case, thank you all for your quick responses and for the support!

Victor

On Sat, Jul 2, 2016 at 8:28 PM, Vladimir Sitnikov <sitnikov.vladimir@gmail.com> wrote:


> The problem is that, even if I set the reltuples and relpages of my choice, when I run the EXPLAIN clause for a query in which the 'newTable'  is involved in (e.g. EXPLAIN SELECT * FROM newTable), I get the same cost and row estimation.

>Could anyone help me with that?


There's a pg_dbms_stats extension that enables you to override/freeze the statistics: https://github.com/ossc-db/pg_dbms_stats

Vladimir



--
Victor Giannakouris - Salalidis

Researcher
Computing Systems Laboratory (CSLab),
National Technical University of Athens

pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: Reviewing freeze map code
Next
From: Vladimir Borodin
Date:
Subject: Re: [PERFORM] 9.4 -> 9.5 regression with queries through pgbouncer on RHEL 6