"Tom Lane" <[EMAIL PROTECTED]> writes:
> It's been clear for quite awhile that a stats target of 10 is often
> too low, but no one has done the legwork to establish what a more
> reasonable tradeoff point would be.
Any ideas on what measurements would be interesting for this?
--
Gregory St
"Greg Sabino Mullane" <[EMAIL PROTECTED]> writes:
> Can we switch the default_statistics_target to a default of 100? Is
> there any reason not to do so at this point?
Other than a 10x increase in the cost of ANALYZE, and in the cost of
histogram-based operations in the planner?
It's been clear f
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Tom Lane replied:
> If there are 100 or more histogram entries it'll do the estimation by
> counting how many of the histogram entries match the pattern, rather
> than using the prefix-range-based estimator (which is pretty much
> all-fantasy an
Hello,
http://archives.postgresql.org/pgsql-bugs/2007-01/msg00160.php
I have met the same bug, and resolved it as follows:
1. Open gpedit.msc
Computer configuration - Windows settings- Security settings-Local
settings- User rights assignment
2. Remove all dead SIDs
3. Rename old folder left fr
