This is currently unsupported in mainstream PostgreSQL, as the WAL only works on the cluster basis. The only options you currently have for performing this is to use the last full backup and copies of WAL files to restore the cluster on a second server to your specific point in time, and restore that copy of the database in question to your primary server.
Jason Minion [EMAIL PROTECTED] -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Monday, February 26, 2007 7:57 AM To: pgsql-admin@postgresql.org Subject: [ADMIN] Recovery/Rollback question Hi, I am new to the list and want to say "hello" first. We are migrating to Postgres and therefore my question might be simple for you. We run several application databases under one db server. Now we are looking for a mechanism to rollback unwanted user command without impact for other databases. Is there a posiibilty to use something like WAL on tablespaces or databases not only on db servers? Does Postgres provide other utilities for this? Which strategies to you use? Scenatio running databases a and b under the server. It is now 10 o 'clock, user made a mistake at 8 o'clock in database a, so we need to roll database a back to 8 o'clock, database b keeps current data status. How do you solve this under Postgres? Any links to useful docu chapters ? Regards, A.Stejskal ---------------------------(end of broadcast)--------------------------- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq ---------------------------(end of broadcast)--------------------------- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
