From: Josh Berkus <josh@agliodbs.com>
To: Tambet Matiisen <t.matiisen@aprote.ee>
Cc: pgsql-performance@postgresql.org
Subject: Re: One tuple per transaction
Date: Sat, 12 Mar 2005 14:05:20 -0800
Message-ID: <200503121405.20943.josh@agliodbs.com> (raw)
In-Reply-To: <A66A11DBF5525341AEF6B8DE39CDE77008804D@black.aprote.com>
References: <A66A11DBF5525341AEF6B8DE39CDE77008804D@black.aprote.com>
Tambet,
> In one of our applications we have a database function, which
> recalculates COGS (cost of good sold) for certain period. This involves
> deleting bunch of rows from one table, inserting them again in correct
> order and updating them one-by-one (sometimes one row twice) to reflect
> current state. The problem is, that this generates an enormous amount of
> tuples in that table.
Sounds like you have an application design problem ... how about re-writing
your function so it's a little more sensible?
--
Josh Berkus
Aglio Database Solutions
San Francisco
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: josh@agliodbs.com, t.matiisen@aprote.ee
Subject: Re: One tuple per transaction
In-Reply-To: <200503121405.20943.josh@agliodbs.com>
* 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