pg.ddx.io pgsql-performance@postgresql.org mailing list archivehelp / color / mirror / Atom feed
From: Richard Huxton <dev@archonet.com>
To: Marc Morin <marc@sandvine.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: partitioning and locking problems
Date: Wed, 01 Feb 2006 09:39:05 +0000
Message-ID: <43E081B9.5050101@archonet.com> (raw)
In-Reply-To: <2BCEB9A37A4D354AA276774EE13FB8C263B3DE@mailserver.sandvine.com>
References: <2BCEB9A37A4D354AA276774EE13FB8C263B3DE@mailserver.sandvine.com>
Marc Morin wrote:
> Under both these circumstances (truncate and create / replace rule) the
> locking behaviour of these commands can cause locking problems for us.
> The scenario is best illustrated as a series of steps:
>
>
> 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).
How much would you get from splitting the view into two: reporting and
inserting?
--
Richard Huxton
Archonet Ltd
view thread (13+ messages) latest in thread
Message-ID: <43E081B9.5050101@archonet.com> Permalink: ../43E081B9.5050101@archonet.com/ Also on: postgresql.org/message-id/43E081B9.5050101@archonet.com ·
reply
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: dev@archonet.com, marc@sandvine.com Subject: Re: partitioning and locking problems In-Reply-To: <43E081B9.5050101@archonet.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