Jaime Casanova wrote:
> we have a some bad queries (developers are working on that), some of
> them run in 17 secs and that is the average but when analyzing logs i
> found that from time to time some of them took upto 3 mins (the same
> query that normally runs in 17secs).
>
> so my question is:
Hi,
We are trying to implement slony as a replication tool for one of our
database. The Insert and updates have increased by approximately double
making some of our important script slow.
The database in concern is a warehouse and we have added additional primary
key to support slony by using def
Hi,
we have a some bad queries (developers are working on that), some of
them run in 17 secs and that is the average but when analyzing logs i
found that from time to time some of them took upto 3 mins (the same
query that normally runs in 17secs).
so my question is: how could i look for contenti
