From: Markus Schaber <schabi@logix-tt.com>
To: Marc Morin <marc@sandvine.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: partitioning and locking problems
Date: Thu, 02 Feb 2006 13:44:23 +0100
Message-ID: <43E1FEA7.8060509@logix-tt.com> (raw)
In-Reply-To: <2BCEB9A37A4D354AA276774EE13FB8C263B3DE@mailserver.sandvine.com>
References: <2BCEB9A37A4D354AA276774EE13FB8C263B3DE@mailserver.sandvine.com>
Hi, Marc,
Marc Morin wrote:
> 1- long running report is running on view
> 2- continuous inserters into view into a table via a rule
> 3- truncate or rule change occurs, taking an exclusive lock.
> Must wait for #1 to finish.
> 4- new reports and inserters must now wait for #3.
> 5- now everyone is waiting for a single query in #1. Results
> in loss of insert data granularity (important for our application).
Apart from having two separate views (one for report, one for insert) as
Richard suggested:
If you have fixed times for #3, don't start any #1 that won't finish
before it's time for #3.
You could also use the LOCK command on an empty lock table at the
beginning of each #1 or #3 transaction to prevent #3 from getting the
view lock before #1 is finished.
HTH,
Markus
--
Markus Schaber | Logical Tracking&Tracing International AG
Dipl. Inf. | Software Development GIS
Fight against software patents in EU! www.ffii.org www.nosoftwarepatents.org
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: schabi@logix-tt.com, marc@sandvine.com
Subject: Re: partitioning and locking problems
In-Reply-To: <43E1FEA7.8060509@logix-tt.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