Adrian Klaver <adrian.klaver@aklaver.com> writes:
> On 09/10/2016 03:59 AM, Kiran wrote:
>> What could be the problem ? Why trigger is not working if I insert from the
>> application ? Am I doing anything wrong ?
> If you have not, turn on log_statement:
> https://www.postgresql.org/docs/9.5/static/runtime-config-logging.html#RUNTIME-CONFIG-LOGGING-WHAT
> Then check your log to see what the application is sending to the database.
At a slightly higher level: everything you've shown us looks fine,
therefore the problem is in something you didn't show us. I've seen
people have problems like this for all sorts of reasons, eg
1. Application isn't connecting to the same database as your manual
sessions. Maybe not even the same server.
2. Application is using a different search_path setting and therefore
touching a different table (same name but other schema).
3. Application isn't issuing the command you think it is, or is failing
to commit it.
4. Trigger is firing as expected but something else is overriding its
change to the data.
Adrian's suggestion of watching log_statement output would help debug
some of these cases; possibly log_connections would help with others.
I'd also suggest checking to see if the application is subject to
different ALTER USER ... SET parameters than your manual session.
Lastly, RAISE NOTICE is a tried-and-true method of checking whether
a trigger is firing, but it's not too helpful for debugging queries
from applications because they invariably drop notices on the floor.
I'd try RAISE LOG instead, and again watch the server log to see what
the application is really doing.
regards, tom lane