Almost. The doc you referred me to describes a pgsql write-ahead log (WAL), which is what Oracle dba's call a redo log. An archive log is a copy of a redo log. According to the WAL doc, pgsql has not yet implemented archive logs, but they are under consideration for a future release.
Archive logs let you do several things, such as complete recovery, point-in-time recovery, hot backups, and transaction histories (log mining.)
Dang! I had no idea PostgreSQL was that advanced. Thanks for the reply. Looks like I need to overcome my fear (read: get off my lazy butt) and check it out. But the no archive log mode is a show stopper. Can't guarantee recovery without it.
Automatic undo management is a feature new to 9i that replaces ye olde rollback segments. If you create your 9i database correctly, you need never worry about undo (rollback) again. It's very nice.
Let me be up front: I am an Oracle slave. I have not and do not work for Oracle, but my Oracle dba and development expertise is vast and is the focal point of my entire career, which essentially rides on Mr. Ellison's coattails. I have been wanting to check out PostgreSQL for some time now, but I suffer major panic attacks whenever I start to download it. I promise to work closely with my therapist to overcome this disability. Perhaps the news about its new replication features will be just the thing I need to overcome my "issues".
I feel better getting that off my chest. Now let me school you little punk beotch newbie dba-wannabes on the what's and wherefore's of enterprise class database administration. Rule #1: Protect Your Data! There is no rule #2. The real reason so many corporations use Oracle is that, if you know what you're doing (and so many of you obviously haven't the first clue), Oracle RDBMS will always be able to recover any committed transaction no matter how severe or catastrophic the failure. Can you say, "archive log mode?" If not, I cannot in good conscience say that you can protect a companies most valuable asset--it's data.
And another thing, while I'm hot on a rant, protecting the data against server or disk failure is one thing, but protecting it against the vagaries of doofus programmers is quite another thing entirely. A good dba accomplishes this via something called database constraints, at which Oracle excels. Can you say, "foreign key?" If not, eventually your database will resemble swiss cheese, with less referential integrity than President Bush's Iraqi WMD speeches.
Finally, everyone is always comparing MySQL and PostgreSQL's runtime performance to Oracle's. Please keep in mind that a database with only a handful of tables and no referential integrity is little more than a file system, and I do not care how many millions of records you stuff into the tables. Grownup databases contain hundreds of tables with multiple schemas and very complex data models. Can MySQL or PostgreSQL handle thousands of requests per second on a grownup database? I would really like to find out for myself.
Finally finally, does PostgreSQL's feature list truly compare with Oracle's? Here is a short list of Oracle features that I cannot live without:
Replication is the process of copying transactions from one source database to one or more target databases on a near-real-time basis, in an effort to keep all or part of the databases tightly synchronized. It is often used to balance the load across multiple database servers, or to share data amonst various divisions within an enterprise. It is pretty simple when all of the target databases only read the replicated data ("single master mode".) It gets trickier when more than one database can update the same record ("multi-master mode".) In the latter case, you need some sophisticated software to detect and resolve conflicts when two or more databases try to update the same record at the same time.
MikeXpop asks a very good question. What he is "implying here" is: Apple does not want us to know how the G5 compares to the G4.
And I have no idea how you can misconstrue him to say, "that the G4 might be faster than the G5". He wants to know if the price difference between the G4 and the G5 is worth the performance difference.
Slashdot Mirror
what if we all had our own little hydrogen generators in our backyards, powered by our own little windmills or photocells? wouldn't that be lovely?
let the love flow.
Archive logs let you do several things, such as complete recovery, point-in-time recovery, hot backups, and transaction histories (log mining.)
Automatic undo management is a feature new to 9i that replaces ye olde rollback segments. If you create your 9i database correctly, you need never worry about undo (rollback) again. It's very nice.
I feel better getting that off my chest. Now let me school you little punk beotch newbie dba-wannabes on the what's and wherefore's of enterprise class database administration. Rule #1: Protect Your Data! There is no rule #2. The real reason so many corporations use Oracle is that, if you know what you're doing (and so many of you obviously haven't the first clue), Oracle RDBMS will always be able to recover any committed transaction no matter how severe or catastrophic the failure. Can you say, "archive log mode?" If not, I cannot in good conscience say that you can protect a companies most valuable asset--it's data.
And another thing, while I'm hot on a rant, protecting the data against server or disk failure is one thing, but protecting it against the vagaries of doofus programmers is quite another thing entirely. A good dba accomplishes this via something called database constraints, at which Oracle excels. Can you say, "foreign key?" If not, eventually your database will resemble swiss cheese, with less referential integrity than President Bush's Iraqi WMD speeches.
Finally, everyone is always comparing MySQL and PostgreSQL's runtime performance to Oracle's. Please keep in mind that a database with only a handful of tables and no referential integrity is little more than a file system, and I do not care how many millions of records you stuff into the tables. Grownup databases contain hundreds of tables with multiple schemas and very complex data models. Can MySQL or PostgreSQL handle thousands of requests per second on a grownup database? I would really like to find out for myself.
Finally finally, does PostgreSQL's feature list truly compare with Oracle's? Here is a short list of Oracle features that I cannot live without:
Replication is the process of copying transactions from one source database to one or more target databases on a near-real-time basis, in an effort to keep all or part of the databases tightly synchronized. It is often used to balance the load across multiple database servers, or to share data amonst various divisions within an enterprise. It is pretty simple when all of the target databases only read the replicated data ("single master mode".) It gets trickier when more than one database can update the same record ("multi-master mode".) In the latter case, you need some sophisticated software to detect and resolve conflicts when two or more databases try to update the same record at the same time.
MikeXpop asks a very good question. What he is "implying here" is: Apple does not want us to know how the G5 compares to the G4. And I have no idea how you can misconstrue him to say, "that the G4 might be faster than the G5". He wants to know if the price difference between the G4 and the G5 is worth the performance difference.