From: | Dean Myerson <dean(at)deanmyerson(dot)org> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Creating and managing triggers |
Date: | 2012-10-08 21:50:20 |
Message-ID: | 50734A9C.2080004@deanmyerson.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
I need to create some triggers and the docs seem pretty straightforward.
When I tried to create one using CREATE TRIGGER, it took over 20
minutes, and the second one hadn't finished over more than an hour. And
I later found that all other database users in the company were locked
out during this process. The table getting the triggers has about 187000
rows in it and is pretty central, so lots of functions join with it.
So the first question is whether it is normal for a Create Trigger
command to take so long. Also, I don't see any commands to examine
existing triggers. They restarted the database server when the second
create trigger hung, so I don't know what happened with it. I didn't
even save the name, obviously a problem on my part. But there should be
some equivalent of Show Trigger, shouldn't there?
Dean
From | Date | Subject | |
---|---|---|---|
Next Message | Ralf Schuchardt | 2012-10-08 21:53:08 | Re: [Mac OS X Mountain Lion] FATAL: could not create shared memory segment: Cannot allocate memory |
Previous Message | Merlin Moncure | 2012-10-08 20:55:28 | Re: Suggestions for the best strategy to emulate returning multiple sets of results |