Skip site navigation (1) Skip section navigation (2)

Re: Recovery/Rollback question

From: "Jason Minion" <jason(dot)minion(at)sigler(dot)com>
To: <Antje(dot)Stejskal(at)ppimedia(dot)de>,<pgsql-admin(at)postgresql(dot)org>
Subject: Re: Recovery/Rollback question
Date: 2007-02-26 19:15:26
Message-ID: (view raw or whole thread)
Lists: pgsql-admin
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

Jason Minion

-----Original Message-----
From: pgsql-admin-owner(at)postgresql(dot)org
[mailto:pgsql-admin-owner(at)postgresql(dot)org] On Behalf Of
Sent: Monday, February 26, 2007 7:57 AM
To: pgsql-admin(at)postgresql(dot)org
Subject: [ADMIN] Recovery/Rollback question


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
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


---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?


In response to


pgsql-admin by date

Next:From: Scott MarloweDate: 2007-02-26 19:44:46
Subject: Re: Recovery/Rollback question
Previous:From: Peter EisentrautDate: 2007-02-26 19:06:30
Subject: Re: host name?

Privacy Policy | About PostgreSQL
Copyright © 1996-2015 The PostgreSQL Global Development Group