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

Re: How to know a table has been modified?

From: Pavan Deolasee <pavan(dot)deolasee(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-27 17:43:39
Message-ID: CABOikdP01CiA6Fc8NL7CFKyq6CmVYf1EEKRtk=3-+ShQ8eoOEw@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
On Mon, Feb 27, 2012 at 9:35 PM, Tatsuo Ishii <ishii(at)postgresql(dot)org> wrote:

> 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
>
>
Would looking into currently held locks help ? You might get some false
positive because the transaction may have acquired a lock, but did not do
any modification. But if you can live with that, it might be worth
considering.

Thanks,
Pavan

-- 
Pavan Deolasee
EnterpriseDB     http://www.enterprisedb.com

In response to

Responses

pgsql-hackers by date

Next:From: Greg SmithDate: 2012-02-27 18:47:29
Subject: Re: pgstat documentation tables
Previous:From: Robert HaasDate: 2012-02-27 17:35:28
Subject: Re: [PATCH] Cleanup: use heap_open/heap_close consistently

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