Re: dropping partitioned table waits forever

From: "Sriram Dandapani" <sdandapani(at)counterpane(dot)com>
To: "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com>
Cc: <pgsql-admin(at)postgresql(dot)org>
Subject: Re: dropping partitioned table waits forever
Date: 2006-08-15 23:00:33
Message-ID: 6992E470F12A444BB787B5C937B9D4DF0574F899@ca-mail1.cis.local
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Postmaster was automatically restarted. (didn't crash).

Rules are used to implement the partitioning (and the triggers as well)

Using postgres 8.1.2

-----Original Message-----
From: Jim C. Nasby [mailto:jnasby(at)pervasive(dot)com]
Sent: Tuesday, August 15, 2006 3:29 PM
To: Sriram Dandapani
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: [ADMIN] dropping partitioned table waits forever

On Tue, Aug 15, 2006 at 02:34:57PM -0700, Sriram Dandapani wrote:
> When I modify the trigger, I noticed that postgres restarted. Not sure
> why, but it happens when it is being executed. This behaviour is
> consistent.

Restarted as in the database crashed??

Is this actually being done with a trigger or with rules?
--
Jim C. Nasby, Sr. Engineering Consultant jnasby(at)pervasive(dot)com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Chris Mair 2006-08-15 23:52:45 Re: psql: FATAL: Database "postgres" does not exist in
Previous Message John Vandervliet 2006-08-15 22:53:05 Re: psql: FATAL: Database "postgres" does not exist in the