From: | "Albe Laurenz" <laurenz(dot)albe(at)wien(dot)gv(dot)at> |
---|---|
To: | <u235sentinel(at)gmail(dot)com>, <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Postgres Triggers issue |
Date: | 2010-02-11 09:57:39 |
Message-ID: | D960CB61B694CF459DCFB4B0128514C203938171@exadv11.host.magwien.gv.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
u235sentinel wrote:
> I have a strange problem we noticed the other day with
> triggers. We're
> running 8.3.3 on Solaris 10 (intel) and have a feed that comes in
> regularly to populate a table we're working on. The feed works just
> fine inserting rows however the following trigger stops the feed until
> we remove the trigger. Any thoughts on what I'm doing wrong here?
>
> Thanks!
>
> ---
>
> CREATE OR REPLACE FUNCTION r.m_t()
> RETURNS trigger AS
> $BODY$
> BEGIN
> INSERT INTO temp_m_t VALUES (NEW.*,1+1);
> RETURN NULL;
> END;
> $BODY$
> LANGUAGE 'plpgsql';
>
>
> CREATE TRIGGER tafter
> AFTER INSERT OR UPDATE
> ON r.m_a
> FOR EACH ROW
> EXECUTE PROCEDURE r.m_t();
What do you mean "stops the feed"?
Can you describe the behaviour in database terms?
What exactly happens, and how does it differ from what you expect?
Are there error messages? If yes, could you quote them?
Yours,
Laurenz Albe
From | Date | Subject | |
---|---|---|---|
Next Message | db.subscriptions | 2010-02-11 11:00:19 | PostgreSQL Installation |
Previous Message | Thomas Kellerer | 2010-02-11 08:59:33 | Re: migrating data from 8.4 to 8.3 |