PostgreSQL is considered by many to be the most advanced open source database in the world (sorry mySQL), providing a wealth of features (sub-select, transactions, write-ahead logging etc) that are usually only found in commercial databases. PostgreSQL is an object-relational database management system (ORDBMS), originally developed in 1977 by the University of Berkeley and it is included by default as the main database on most *BSD systems, like FreeBSD. But in spite of its long history and extensive user base (however, it is still not as popular as the Linux-centric mySQL though), PostgreSQL suffered from a lack of comprehensive and easy-to-use documentation. "Practical PostgreSQL" (along with 2 more PostgreSQL books, all released the last 2-3 months) fills that information void with a fast-paced guide to installation, configuration, and usage.

You knew what Eugenia was talking about, didn't you? Then, quit being so quick to point out spelling errors! I'd like to see all of the people who point out stuff like that to try and do what she does - write technical articles in a language other than their native one, and see how well they do... I'm pretty sure that the majority won't be anywhere as proficient (I'm including myself - I can barely get by in English, let alone anything else!)

The book is poor. Really, really poor. People practically perpetrating PostgreSQL (sorry, couldn't resist need a lot more than this book in order to get anywhere. The book simply fails to cover very much of the details I hoped to see. Very little information on best practices, tuning, nitty-gritty under-the-hood info, very little information on programming against PostgreSQL, and a lot of fluff at the end about a payware, so-simple-it-can't-do-much "application server" that reads like an ad. Rarely have I been so offended by a book. A large part of my indignation comes from the fact that the book is published by O'Reilly -- I expect *so* much better from them, I can only think that somehow they got hoodwinked by Command Prompt.

As a hint to all PostgreSQL users, just read the online version of the book, don't bother to buy a copy. Or better yet, go to www.postgresql.org and read the online documentation. In parts it is sparse, old, or needs improvement, but it strives to be comprehensive and succeeds moderately well. It is also usable and constantly improving.

I cannot recommend the other books on the market, because I haven't read them, but I will be looking into them to see if they cover more information in a more useful manner.