Database recovery from write ahead logs is only supported in PostgreSQL
8.0.0 and later.
---
hi
I have to setup some backup policies for our postgres server.
I had a few queries regarding corruption of database.
what are the ste
y original
assumption, or whether the current WAL is in fact the most recently
modified.
Apologies if I'm missing something really obvious, but I've searched the
mail archives and the web and haven't been able to find anything relevant.
Regards
Thomas Revell
:.
OK, thanks.
[EMAIL PROTECTED] writes:
> I'm currently looking at using WAL / PITR backups for a database, and I
> need to keep the backups as up to date as possible. As such, keeping a
> copy of the current WAL file, as suggested in the manual, would seem to
be
> a very good idea. I'm
ast)---
>TIP 2: you can get off all lists at once with the unregister command
>(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
Hopefully this helps you.
Regards
Thomas Revell
:.___
CONFIDENTIALITY : This e-mail and any atta
Hi,
we are fascinated about the point in time recovery feature. In order to
have
that feature for each database(schema) extra and to make them disturb each
other even less, we would like to run several postmasters. So for each
DB-schema (3) there should be an extra DBMS running (in an own PGDATA
See the psql documentation:
http://www.postgresql.org/docs/8.0/interactive/app-psql.html
-W
--password
Cause psql to prompt for a password before connecting to a database. This
will remain set for the entire session, even if you change the database
connection with the meta-command \connect.
I
Well, my French isn't as good as I'd like :) but it looks as though you're
trying to set up the database as an administrator. As this creates various
security risks, it's not allowed. You probably created a user account
during PostgreSQL installation. If you run initdb as that user, you should
