From: tfinneid@ifi.uio.no
To: pgsql-performance@postgresql.org
Subject: Re: improvement suggestions for performance design
Date: Thu, 5 Jul 2007 17:49:29 +0200 (CEST)
Message-ID: <41319.134.32.140.234.1183650569.squirrel@webmail.uio.no> (raw)
In-Reply-To: <b09064f30707050757p21c881eamf5e2068578499cc8@mail.gmail.com>
References: <40362.134.32.140.234.1183637748.squirrel@webmail.uio.no>
<468CEB32.30109@enterprisedb.com>
<40891.134.32.140.234.1183642557.squirrel@webmail.uio.no>
<b09064f30707050757p21c881eamf5e2068578499cc8@mail.gmail.com>
> On 7/5/07, tfinneid@ifi.uio.no <tfinneid@ifi.uio.no> wrote:
>
> I don't know much about this EAV stuff. Except to say that my company is
> in
> a situation with a lot of adds and bulk deletes and I wish the tables were
> designed with partitioning in mind. That is if you know how much, order of
> magnitude, data each table will hold or will pass through (add and
> delete),
> you may want to design the table with partitioning in mind. I have not
> done
> any partitioning so I cannot give you details but can tell you that mass
> deletes are a breeze because you just "drop" that part of the table. I
> think
> it is a sub table. And that alleviates table bloat and excessive
> vacuuming.
By partitioning, do you mean some sort of internal db table partitioning
scheme or just me dividing the data into different tables?
There want be many deletes, but there might of course be some.
Additionally, because of the
performance requirements, there wont be time to run vacuum in between the
insert, except for in non-operational periods. which will only be a couple
of hours during the day. So vacuum will have to be scheduled at those
times, instead of the normal intervals.
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-performance@postgresql.org
Cc: tfinneid@ifi.uio.no
Subject: Re: improvement suggestions for performance design
In-Reply-To: <41319.134.32.140.234.1183650569.squirrel@webmail.uio.no>
References: <40362.134.32.140.234.1183637748.squirrel@webmail.uio.no> <468CEB32.30109@enterprisedb.com> <40891.134.32.140.234.1183642557.squirrel@webmail.uio.no> <b09064f30707050757p21c881eamf5e2068578499cc8@mail.gmail.com> <41319.134.32.140.234.1183650569.squirrel@webmail.uio.no>
* 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