On 10/19/06, Jens Schipkowski <[EMAIL PROTECTED]> wrote:
On Thu, 19 Oct 2006 19:32:22 +0200, Merlin Moncure > > 1. your database design
is the real culprit here. If you want things
> to run really quickly, solve the problem there by normalizing your
> schema. denomalization is the root cause of
On Thu, 19 Oct 2006 19:32:22 +0200, Merlin Moncure <[EMAIL PROTECTED]>
wrote:
On 10/19/06, Jens Schipkowski <[EMAIL PROTECTED]> wrote:
// select finds out which one has not an twin
// a twin is defined as record with the same attr* values
// decreases speed over time until timeout by postgres
On 10/19/06, Jens Schipkowski <[EMAIL PROTECTED]> wrote:
// select finds out which one has not an twin
// a twin is defined as record with the same attr* values
// decreases speed over time until timeout by postgresql
SELECT *
FROM tbl_reg reg
WHERE register <> loc1 AND
idreg NOT IN
On Thu, 19 Oct 2006 16:55:34 +0200, Richard Huxton
wrote:
Jens Schipkowski wrote:
Hi,
we've got performance problems due to repeating SELECT, UPDATE,
DELETE, INSERT statements. This statements have to be executed every 10
seconds, but they run into a timeout.
To obviate problems regardi
