From: Ivan Voras <ivoras@freebsd.org>
To: pgsql-performance@postgresql.org
Subject: Re: Inserts in 'big' table slowing down the database
Date: Mon, 03 Sep 2012 13:21:36 +0200
Message-ID: <k223s0$e83$1@ger.gmane.org> (raw)
In-Reply-To: <CAFcOn2_W6v_vqwomCf6DEtXk=N8iB5WU-7XEdcYgX-VFUE32+Q@mail.gmail.com>
References: <CAFcOn2_W6v_vqwomCf6DEtXk=N8iB5WU-7XEdcYgX-VFUE32+Q@mail.gmail.com>
On 03/09/2012 13:03, Stefan Keller wrote:
> Hi,
>
> I'm having performance issues with a simple table containing 'Nodes'
> (points) from OpenStreetMap:
>
> CREATE TABLE nodes (
> id bigint PRIMARY KEY,
> user_name text NOT NULL,
> tstamp timestamp without time zone NOT NULL,
> geom GEOMETRY(POINT, 4326)
> );
> CREATE INDEX idx_nodes_geom ON nodes USING gist (geom);
>
> The number of rows grows steadily and soon reaches one billion
> (1'000'000'000), therefore the bigint id.
> Now, hourly inserts (update and deletes) are slowing down the database
> (PostgreSQL 9.1) constantly.
> Before I'm looking at non-durable settings [1] I'd like to know what
> choices I have to tune it while keeping the database productive:
> cluster index? partition table? use tablespaces? reduce physical block size?
You need to describe in detail what does "slowing down" mean in your
case. Do the disk drives somehow do more operations per transaction?
Does the database use more CPU cycles? Is there swapping? What is the
expected (previous) performance?
At a guess, it is very unlikely that using non-durable settings will
help you here.
Attachments:
signature.asc (application/pgp-signature, 259B) download
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: ivoras@freebsd.org
Subject: Re: Inserts in 'big' table slowing down the database
In-Reply-To: <k223s0$e83$1@ger.gmane.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox