Re: [PERFORM] Discovering the most searched values for a field

2012-01-13 Thread Josh Berkus
On 1/13/12 10:08 AM, alexandre - aldeia digital wrote: > Hi, > > Is there a simple way (or a tool) to discover the most searched values > in a field from a table ? > > In the pg_stats, I can see the most common values generated by ANALYZE, > but I want to know how many queries are using this valu

Re: [PERFORM] Partitioning by status?

2012-01-13 Thread Josh Berkus
On 1/13/12 2:44 AM, alexandre - aldeia digital wrote: >> >> Also, (2) only really works if you're going to obsolesce (remove) >> archive records after a certain period of time. Otherwise the >> sub-partitioning hurts performance. >> > > Is there any moves to include the "easy" table partitioning

[PERFORM] Discovering the most searched values for a field

2012-01-13 Thread alexandre - aldeia digital
Hi, Is there a simple way (or a tool) to discover the most searched values in a field from a table ? In the pg_stats, I can see the most common values generated by ANALYZE, but I want to know how many queries are using this values. With this information and the other statistics, I want to cr

Re: [PERFORM] auto vacuum, not working?

2012-01-13 Thread Kevin Grittner
Mario Weilguni wrote: >> yesterday I delete about 200 million rows of a table >> How can I release the space used by deleted rows? >> Without block the table. > vacuum does not reclaim space, just marks tuples dead. You need > vacuum full. VACUUM FULL will lock the table, blocking all othe

Re: [PERFORM] auto vacuum, not working?

2012-01-13 Thread Mario Weilguni
Am 13.01.2012 13:08, schrieb Anibal David Acosta: Hi, yesterday I delete about 200 million rows of a table (about 150GB of data), after delete completes the autovacuum process start. The autovacuum is running for about 11 hours but no space is released Autovacuum parameters are with default

[PERFORM] auto vacuum, not working?

2012-01-13 Thread Anibal David Acosta
Hi, yesterday I delete about 200 million rows of a table (about 150GB of data), after delete completes the autovacuum process start. The autovacuum is running for about 11 hours but no space is released Autovacuum parameters are with default values in postgresql.conf The postgres version is

Re: [PERFORM] Partitioning by status?

2012-01-13 Thread alexandre - aldeia digital
Also, (2) only really works if you're going to obsolesce (remove) archive records after a certain period of time. Otherwise the sub-partitioning hurts performance. Is there any moves to include the "easy" table partitioning in the 9.2 version ? -- Sent via pgsql-performance mailing list (