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

Re: How to know a table has been modified?

From: Shigeru Hanada <shigeru(dot)hanada(at)gmail(dot)com>
To: Tatsuo Ishii <ishii(at)postgresql(dot)org>
Cc: lennin(dot)caro(at)yahoo(dot)com, Kevin(dot)Grittner(at)wicourts(dot)gov, pgsql-hackers(at)postgresql(dot)org
Subject: Re: How to know a table has been modified?
Date: 2012-02-28 07:44:08
Message-ID: 4F4C85C8.5000303@gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
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.

    https://github.com/snaga/xlogdump

-- 
Shigeru Hanada


In response to

pgsql-hackers by date

Next:From: Shigeru HanadaDate: 2012-02-28 07:46:54
Subject: Re: pgsql_fdw, FDW for PostgreSQL server
Previous:From: Fujii MasaoDate: 2012-02-28 06:21:12
Subject: Re: xlog location arithmetic

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