Free online postgreSQL book 1608

Aquila Deus

"Role based" security has always seemed problematic to me. Its more trouble than its worth, IMHO. If you want to use it, fine, it is just a metaphor I find a bit too convoluted.

I wasn't sure what you meant by analysis, there are many aspects of databases which are called "analysis." As for OLAP, PostgreSQL is pretty awesome. I've written some extensions, and the contrib stuff is nice too.

How does not not work well?

WTF? Cite please.

There are plenty of "GUI" administration tools out there, PgAdmin comes to mind. It works pretty well.

No, one single database is 60 gig. I have others that are 5 or 10 gig as well.

When I say I need a "real" database, I'm not fooling around.

No, those would be nice, but also the reality is with technology like RAID there is little real need for parbreastioning. "Parallel query" is nice if you are using a server will little or no load, but on an active server the performance benefit is less.

Backup and restore on PostgreSQL is one of the things I think it does really well. I'm not sure what they mean by "better scaling" in terms of database size or server size or number of users, PostgreSQL's MVCC and process model scales very well. Without details about why those statements are made I can evaluate their accuracy.

Storage management? Maybe in the past, but they FINALY got table spaces in. (I have been pushing that for a while), however, you could always have done the equivilent manually.

User management may be an issue for some, but you can log everything. The query details are cool, you can log every query as it is happening as well as its plan and end time.

What is "sp" as used in this sentence?