On Tue, 12 Feb 2002, David Griffiths wrote:
> I am new to Postgres (we are looking at swaping out our Oracle databases to
> save on the repressive licencing fees).
>
> Archive logging is not just for database recovery - it can be used to
> implement standby databases. Archived redo logs is one of the bigger gaps,
> as we use standby databases to help maintain 24x7 (or our best attempt at).
You can implement standby databases by dumping the production db and
recovering the standby db. But, of course, it depends of the amounts of
data if this can be done frequently.
> Of course, adding this feature is one more step away from the features you
> like (a fast, reliable, easy-to-administer database) and one step closer to
> an Oracle database (slower, less reliable, and harder to administer).
I cannot see any reason why a select should be slower when archive logs
are written. Even when updating a db, archive logs can IMHO be done by
switching the WAL and keeping it instead of writing to the WAL *and* an
additional log that is to be archived.
