Dear List,
does pgsql maintains statistics on index usage? I mean just a counter
for each index in the database, incremented each time time it is used.
It would be useful to help cleaning almost unused index and to avoid
poisoning the global cache.
I've found nothing so far but may be I've been m
Dear List,
Thank you for all for your advices, even if there's not a direct and
magical solution, I've now some paths to try.
I really enjoy the PostgreSQL community.
Wish you a nice day/night, best regards.
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make chang
Le 18/05/2015 17:20, William Dunn a écrit :
Hello William,
Hello François - the CLUSTER command doesn't have to do with where your
indexes are. What the CLUSTER command does is physically sort the table
data based on the index (Doc:
http://www.postgresql.org/docs/devel/static/sql-cluster.html).
Le 18/05/2015 16:38, William Dunn a écrit :
Thank you William,
* With read-only work loads you can make shared_buffers very large,
like 40% of RAM available to the database. Usually you would keep it
lower because in a write heavy workload large shared_buffers causes
checkpoints t
Le 18/05/2015 16:20, Andreas Kretschmer a écrit :
Thank you Andreas,
you can set fillfactor to 100
Yes, but it's already the default value according to documentation.
And you can disable VACUUM.
Already done ;-)
I was more dreaming of something like "disable read write locks or
mutexes"
Dear List,
I would like to know if somebody is aware of tricks for optimizing
PostgreSQL settings for a read-only database.
I have a big read-only database (> 1.10^9 records splitted into ~ 10
tables) using GiST and Btree indexes, no foreign keys on tables at all.
I believe that not doing loc
