Newbie question about degraded performance on delete statement.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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 simple:
delete from table where pk = ?

The explain query report a single index scan on the primary key index,
as expected.

I have run vacuum using the pgAdmin tool, but to no avail.

I have also dropped and recreated the indexes, again without any benefit.

I have later created a copy of the table using the "create table
table_copy as select * from table" syntax.

Matching the configuration of the original table also on the copy
(indexes and constraints), I was able to delete the raws from the new
table with regular performances, from 20 to 100 times faster than
deleting from the original table.

Given this evidence, what are the best practices to fix/avoid this
kind of problems?

I am using PostgreSQL 8.1.4 both on Linux (on a Parallels virtual
machine with a Linux OS) and on Solaris, on a hosted zone; the Solaris
version is running the live DB, while the Linux instance is on my
development machine using a snapshot of the live data.

Thanks for your attention.

Best regards,

Giulio Cesare Solaroli

---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster

[Postgresql General]     [Postgresql PHP]     [PHP Users]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Yosemite]

  Powered by Linux