| From: | "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com> |
|---|---|
| To: | Sriram Dandapani <sdandapani(at)counterpane(dot)com> |
| Cc: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: dropping partitioned table waits forever |
| Date: | 2006-08-15 22:28:37 |
| Message-ID: | 20060815222836.GX21363@pervasive.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | John Vandervliet | 2006-08-15 22:53:05 | Re: psql: FATAL: Database "postgres" does not exist in the |
| Previous Message | John Vandervliet | 2006-08-15 21:48:43 | psql: FATAL: Database "postgres" does not exist in the system catalog. |