| 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 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Smith | 2012-02-27 18:47:29 | Re: pgstat documentation tables |
| Previous Message | Robert Haas | 2012-02-27 17:35:28 | Re: [PATCH] Cleanup: use heap_open/heap_close consistently |