2012/2/28 Tatsuo Ishii <[email protected]>:
> Are you suggesting log_statement? I don't think it's a solution by
> following reasons:
>
> 1) it's slow to enable that on busy systems
> 2) tables affected by cascading delete/update/drop is not logged in
> PostgreSQL log
What about reading archived WAL files? They would contain every
delete/update/drop including cascading ones, though it might be too late
because WAL files are not available until archived.
xlogdump would help reading WAL files.
https://github.com/snaga/xlogdump
--
Shigeru Hanada
--
Sent via pgsql-hackers mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
