Skip site navigation (1) Skip section navigation (2)


From: yogesh <yogesh(dot)arora(dot)daffodil(at)gmail(dot)com>
To: pgsql-admin(at)postgresql(dot)org
Date: 2007-10-20 06:00:50
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-admin
On Oct 19, 11:05 pm, scott(dot)marl(dot)(dot)(dot)(at)gmail(dot)com ("Scott Marlowe") wrote:
> On 10/19/07, yogesh <yogesh(dot)arora(dot)daffo(dot)(dot)(dot)(at)gmail(dot)com> wrote:
> > Hello frnds,
> >  I have a trigger on a table with After UPDATE OR INSERT ..that insert
> > a record in an another table..........If the Trigger Fire Correctly
> > the row is inserted or updated in the database as the case is. But if
> > it is not fire correctly then the table is also not updated on which
> > the trigger is..............
> > Is it the right .................?  if yes......How to insert the
> > record in the table if the trigger is failed.
> Yes, it's right.  Triggers are part of a transaction (or run their
> own) so if the trigger fails, so does the transaction.
> If you really need to have something insert rather or not the
> transaction succeeds, you can either use savepoints so that you can
> roll back to before the error then insert the row anyway, or use
> dblink to connect to the db through another backend and commit your
> data that way.
> You might want to give more info on exactly what you're trying to do
> so the folks on the list can make better informed recommendations.
> ---------------------------(end of broadcast)---------------------------
> TIP 9: In versions below 8.0, the planner will ignore your desire to
>        choose an index scan if your joining column's datatypes do not
>        match

Hello Scott,
Thanks to you....
   you got the right point point what i want to know.......

 are you saying about programming or any other way to done insert a row even if the Trigger fails or succeeds

   Yogesh Arora

In response to


pgsql-admin by date

Next:From: yogeshDate: 2007-10-20 10:36:00
Subject: Postgres SQL with Suse Linux
Previous:From: Scott MarloweDate: 2007-10-19 19:05:12
Subject: Re: Cluster/Replication

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group