PostgreSQL is a robust, next-generation, Object-Relational DBMS (ORDBMS), derived from the Berkeley Postgres database management system. "PostgreSQL is one of the best-managed open source projects out there" a friend-in-the-know told me about 2 years ago, so today we feature a mini-interview with five members of the PostgreSQL team about their plans on the popular DB.
Permalink for comment
To read all comments associated with this story, please click here.
pg_dump is non-blocking, and provides a consistent view. Look it up, it's quite good. 1980s tech or not, it's a good backup tool, and it works, which is more than I can say for many of the commercial backup tools I've had to try and make work on other databases.
I know Oracle is the wrong tool for the job around here, and I'm trying to get them to use Postgresql where it makes the most sense, on large indexing systems. Almost all of what Oracle does where I work is indexing of large datasets, and the worse that could happen if the system crashed and burned would be a couple of days of indexing lost.
Funny thing is, if you go around the world, you'll find Oracle doing this kind of brain dead stuff at high prices for the sole reason that it's the tools the developers already know, not that it's a good fit for the job.
My Point on PITR in Postgresql was that it will be BOTH a PITR system, as well as provide the incremental backups, since the data stream for both would be the same, just handled differently.
pg_dump is non-blocking, and provides a consistent view. Look it up, it's quite good. 1980s tech or not, it's a good backup tool, and it works, which is more than I can say for many of the commercial backup tools I've had to try and make work on other databases.
I know Oracle is the wrong tool for the job around here, and I'm trying to get them to use Postgresql where it makes the most sense, on large indexing systems. Almost all of what Oracle does where I work is indexing of large datasets, and the worse that could happen if the system crashed and burned would be a couple of days of indexing lost.
Funny thing is, if you go around the world, you'll find Oracle doing this kind of brain dead stuff at high prices for the sole reason that it's the tools the developers already know, not that it's a good fit for the job.
My Point on PITR in Postgresql was that it will be BOTH a PITR system, as well as provide the incremental backups, since the data stream for both would be the same, just handled differently.