Hello,
thanks to the added info available running the explain plan through
pgsl (instead of using pgAdmin) I was able to realize that an
(implicitly created) trigger was the culprit of the slowdown I was
suffering.
Adding an index on the foreign key the trigger was monitoring solved the issue.
T
Hello Gregory,
On 10/3/07, Greg Williamson <[EMAIL PROTECTED]> wrote:
> Giulio Cesare Solaroli wrote:
> > Hello everybody,
> >
> > I have just joined the list, as I am experiencing a degradation on
> > performances on my PostgreSQL instance, and I was looking for some
> > insights on how to fix/av
Giulio Cesare Solaroli wrote:
Hello everybody,
I have just joined the list, as I am experiencing a degradation on
performances on my PostgreSQL instance, and I was looking for some
insights on how to fix/avoid it.
What I have observed are impossibly high time on delete statements on
some tables
On 2 Oct 2007 at 23:55, Giulio Cesare Solaroli wrote:
> What I have observed are impossibly high time on delete statements on
> some tables.
>
> The delete statement is very simple:
> delete from table where pk = ?
>
> The explain query report a single index scan on the primary key index,
> as e
Hello everybody,
I have just joined the list, as I am experiencing a degradation on
performances on my PostgreSQL instance, and I was looking for some
insights on how to fix/avoid it.
What I have observed are impossibly high time on delete statements on
some tables.
The delete statement is very