postgresqlを使う時に読み返したいDBMS Musings: Announcing release of HadoopDB (longer version)
my students Azza Abouzeid and Kamil Bajda-Pawlikowski developed HadoopDB. It's an open source stack that includes PostgreSQL, Hadoop, and Hive, along with some glue between PostgreSQL and Hadoop, a catalog, a data loader, and an interface that accepts queries in MapReduce or SQL and generates query plans that are processed partly in Hadoop and partly in different PostgreSQL instances spread across many nodes in a shared-nothing cluster of machines. In essence it is a hybrid of MapReduce and parallel DBMS technologies. But unlike Aster Data, Greenplum, Pig, and Hive, it is not a hybrid simply at the language/interface level. It is a hybrid at a deeper, systems implementation level. Also unlike Aster Data and Greenplum, it is free and open source.Install Django, GeoDjango, PostgreSQL & PostGIS on OSX Leopard
Geohacking funPostgreSQL Tips and Tricks | gtuhl: startup technology
Here’s a dozen tips for working with a PostgreSQL database. It is a sophisticated and powerful piece of software and just knowing a few rules of thumb before diving in can be a huge help.
Here’s a dozen tips for working with a PostgreSQL database. It is a sophisticated and powerful piece of software and just knowing a few rules of thumb before diving in can be a huge help. If you want more detail read the amazing documention. My list of tips was very long so I just chopped off a dozen for this post.EXPLAIN EXTENDED: efficient database queries in SQL.
O mica documentatie cum sa faci un warm standby server PostgreSQL pentru HA ca sa replici o baza de dateAre Commercial Databases Worth It? - Coding the Wheel
I've worked with expensive SQL Server and Oracle setups for most of my career. I've defended them viciously against all comers and contrarians. I've participated in late-night guerilla flame wars and drunken bar brawls. And I've sought out with relentless tunnel vision those pieces of propaganda which support my foregone conclusion: that SQL Server and/or Oracle are (or were) the best choices for the organization. I used to be a commercial database advocate. These databases have put food on my table for a dozen years, you see. I am (or was) what you might call an entrenched practicioner, not necessarily an expert, but a practicioner. And in the manner of entrenched practicioners around the world, I've treated you heretics with the sadistic undercutting and poisonous rancor you've deserved! "MySQL?" I would sneer. "PostgreSQL? Thanks, but this a serious project. We need a database we can depend on." Ahem.
googled "why pay for commercial database" and found this among other articles
Are Commercial Databases Worth It? http://bit.ly/Du96H (via @newsycombinator) [from http://twitter.com/tadej/statuses/1664387681]
Se cuestiona la idoneidad de escoger una BD comercial com Oracle o SQL Server frente a sus alternativas Open Source.PERCONA PERFORMANCE CONFERENCE 2009 SCHEDULE :: PERCONA
These are all mysql oriented, but it sure seems like there are some fantastic principles to be pulling from here. Ex "covering indexes; orders-of-magnitude improvements." Or one on optimizing disk i/o.
Slides from a great variety of sessions @ Percona Performance Conference 2009 (April)
slides of the conference are available onlinyrossp.org - Full-text searching in Django with PostgreSQL and tsearch2