2012/2/28 Tatsuo Ishii <ishii(at)postgresql(dot)org>:
> 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.
In response to
pgsql-hackers by date
|Next:||From: Shigeru Hanada||Date: 2012-02-28 07:46:54|
|Subject: Re: pgsql_fdw, FDW for PostgreSQL server|
|Previous:||From: Fujii Masao||Date: 2012-02-28 06:21:12|
|Subject: Re: xlog location arithmetic|