From: Marc Morin <marc@sandvine.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-performance@postgresql.org
Subject: Re: partitioning and locking problems
Date: Wed, 1 Feb 2006 09:25:10 -0500
Message-ID: <2BCEB9A37A4D354AA276774EE13FB8C263B3E5@mailserver.sandvine.com> (raw)
Tom,
Do you mean it would be impossible to change the code so that existing
selects continue to use the pre-truncated table until they commit? Or
just require a more extensive change?
The update/insert rule change appears to be more more doable? No?
> -----Original Message-----
> From: Tom Lane [mailto:tgl@sss.pgh.pa.us]
> Sent: Wednesday, February 01, 2006 12:50 AM
> To: Marc Morin
> Cc: pgsql-performance@postgresql.org
> Subject: Re: [PERFORM] partitioning and locking problems
>
> "Marc Morin" <marc@sandvine.com> writes:
> > Would like to understand the implications of changing postgres'
> > code/locking for rule changes and truncate to not require
> locking out
> > select statements?
>
> It won't work...
>
> regards, tom lane
>
>
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: marc@sandvine.com, tgl@sss.pgh.pa.us
Subject: Re: partitioning and locking problems
In-Reply-To: <2BCEB9A37A4D354AA276774EE13FB8C263B3E5@mailserver.sandvine.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