On 04/25/2011 10:48 AM, Andrew Sullivan wrote:
You can see this in certain items in the top 10. Three, four, five, seven, maybe 8 eight, and ten all seemed to me to be things I've actually done before, but not using something directly inside Postgres.
The idea that something must ship in the database to be useful is really engrained in some people. I do this talk nowadays about common mistakes people make when deploying PostgreSQL, and one of the top items I put on there is not actively investigating external tools.
None of the items on this list would be on my own top list of missing things in PostgreSQL. I see "Better fragmentation management" as a footnote and there's an intro discussion to that on the blog at http://blog.kimiensoftware.com/2011/04/compacting-postgresql-tables/ Apparently the struggles required to sort out a little 25GB table apparently didn't make enough of an impression to put that into its proper place, which is way ahead of every item listed on the suggested missing feature set. Query progress is #1? It's annoying, yes, but so not even close to pole position to me. From reading the blog a bit, it sounds like the author is managing lots of smallish (to me) databases, so putting so much emphasis on making each individual one easier to troubleshoot makes more sense.
-- Greg Smith 2ndQuadrant US greg@xxxxxxxxxxxxxxx Baltimore, MD PostgreSQL Training, Services, and 24x7 Support www.2ndQuadrant.us "PostgreSQL 9.0 High Performance": http://www.2ndQuadrant.com/books -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
