From: Tom Lane <tgl@sss.pgh.pa.us>
To: Sriram Dandapani <sdandapani@counterpane.com>
Cc: Matthew T. O'Connor <matthew@zeut.net>
Cc: pgsql-admin@postgresql.org
Subject: Re: autovacuum ignore tables
Date: Fri, 29 Sep 2006 17:38:07 -0400
Message-ID: <3831.1159565887@sss.pgh.pa.us> (raw)
In-Reply-To: <6992E470F12A444BB787B5C937B9D4DF060E5C05@ca-mail1.cis.local>
References: <6992E470F12A444BB787B5C937B9D4DF060E5C05@ca-mail1.cis.local>
"Sriram Dandapani" <sdandapani@counterpane.com> writes:
> Real question is: Why do the INSERTS go into wait state as soon as the
> lock table statement is issued on the parent?
If you were just inserting directly into other child tables, a lock on
either the parent or the target child table shouldn't affect them.
I wonder if you are using conditional rules to redirect the inserts,
and the rules include a reference to the target table? If that's the
case, you really need to drop the relevant rule before you remove the
child table, anyway.
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, sdandapani@counterpane.com, matthew@zeut.net
Subject: Re: autovacuum ignore tables
In-Reply-To: <3831.1159565887@sss.pgh.pa.us>
References: <6992E470F12A444BB787B5C937B9D4DF060E5C05@ca-mail1.cis.local> <3831.1159565887@sss.pgh.pa.us>
* 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