On Aug 9, 2012, at 7:11 PM, Sergey Konoplev <sergey.konoplev@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote: > On Thu, Aug 9, 2012 at 2:53 PM, Sergey Konoplev > <sergey.konoplev@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote: >>> How can I make the row changes inside the trigger function visible to the top level statement? >> >> your redirecting function is okay. However the only way to get the >> inserted row back is to do it from a subsequent statement in the >> partitioning case. > > BTW I am not completely correct here. There is a solution but it is a > tricky one https://gist.github.com/59067. I am not sure if it is a > good performing one but it will work. I don't think it's a good solution for a partitioned table. Any how, thank you for the information. > >> In your application you can use LISTEN/NOTIFY if you need to get some >> specific information from trigger BTW. May be it will help somehow. >> >> -- >> Sergey Konoplev >> >> a database architect, software developer at PostgreSQL-Consulting.com >> http://www.postgresql-consulting.com >> >> Jabber: gray.ru@xxxxxxxxx Skype: gray-hemp Phone: +79160686204 > > > > -- > Sergey Konoplev > > a database architect, software developer at PostgreSQL-Consulting.com > http://www.postgresql-consulting.com > > Jabber: gray.ru@xxxxxxxxx Skype: gray-hemp Phone: +79160686204 > > -- > Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-admin > -- Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
