On Sat, May 4, 2019 at 02:32:06PM +0900, Ronny Ko wrote:
> Hi,
>
> I am trying to efficiently rollback a manually selectedd subset of committed
> SQL transactions by scanning an SQL transaction log. This feature is useful
> when a database administrator wants to rollback not the entire database
> system,
> but only particular SQL statements that affect a certain set of SQL tables.
> Unfortunately, this is impossible in the current PostgreSQL setup, because
> PostgreSQL's WAL(Write-Ahead Log) file doesn't provide any SQL statement-level
> redo records, but only physical block-level redo records.
My blog entry covers some of this:
https://momjian.us/main/blogs/pgblog/2019.html#March_6_2019
--
Bruce Momjian <br...@momjian.us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +
