Re: [GENERAL] Postgres Triggers issue

2010-02-11 Thread u235sentinel
Adrian Klaver wrote: On Thursday 11 February 2010 1:57:39 am Albe Laurenz wrote: 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.

Re: [GENERAL] Postgres Triggers issue

2010-02-11 Thread u235sentinel
Adrian Klaver wrote: Well that would depend on any number of factors. Without information on how the feed is being done or more detailed logs it is hard to say for sure. At a guess though, I would say it is because the 'feed' is being done wrapped in a transaction and when the trigger errors

Re: [GENERAL] Postgres Triggers issue

2010-02-11 Thread Adrian Klaver
On 02/11/2010 11:08 AM, u235sentinel wrote: Trigger function for an insert/update trigger should return "NEW", not NULL (OLD - for "on delete" trigger): It's an AFTER TRIGGER, so the RETURN-Value ignored. According the doc: The return value of a BEFORE or AFTER statement-level trigger or an

Re: [GENERAL] Postgres Triggers issue

2010-02-11 Thread u235sentinel
Trigger function for an insert/update trigger should return "NEW", not NULL (OLD - for "on delete" trigger): It's an AFTER TRIGGER, so the RETURN-Value ignored. According the doc: The return value of a BEFORE or AFTER statement-level trigger or an AFTER row-level trigger is always

Re: [GENERAL] Postgres Triggers issue

2010-02-11 Thread Andreas Kretschmer
A. Kretschmer wrote: > In response to Igor Neyman : > > > > > > CREATE TRIGGER tafter > > > AFTER INSERT OR UPDATE > > > ON r.m_a > > > FOR EACH ROW > > > EXECUTE PROCEDURE r.m_t(); > > > > > > > > > > Trigger function for an insert/update trigger should return "NEW", not > > NULL (OLD - for

Re: [GENERAL] Postgres Triggers issue

2010-02-11 Thread A. Kretschmer
In response to Igor Neyman : > > > > CREATE TRIGGER tafter > > AFTER INSERT OR UPDATE > > ON r.m_a > > FOR EACH ROW > > EXECUTE PROCEDURE r.m_t(); > > > > > > Trigger function for an insert/update trigger should return "NEW", not > NULL (OLD - for "on delete" trigger): It's an AFTER TRIGGER, s

Re: [GENERAL] Postgres Triggers issue

2010-02-11 Thread Igor Neyman
> -Original Message- > From: u235sentinel [mailto:u235senti...@gmail.com] > Sent: Wednesday, February 10, 2010 11:15 PM > To: pgsql-general@postgresql.org > Subject: Postgres Triggers issue > > I have a strange problem we noticed the other day with > triggers. We're running 8.3.3 on So

Re: [GENERAL] Postgres Triggers issue

2010-02-11 Thread Adrian Klaver
On Thursday 11 February 2010 1:57:39 am Albe Laurenz wrote: > 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

Re: [GENERAL] Postgres Triggers issue

2010-02-11 Thread Albe Laurenz
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 th

[GENERAL] Postgres Triggers issue

2010-02-10 Thread u235sentinel
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 tri