Re: Trigger is not working for Inserts from the application

From: Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com>
To: Kiran <bangalore(dot)kiran(at)gmail(dot)com>, <pgsql-general(at)postgresql(dot)org>
Subject: Re: Trigger is not working for Inserts from the application
Date: 2016-09-11 02:16:02
Message-ID: bb4ecf09-5f32-ba61-b999-d635d75090b9@BlueTreble.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 9/10/16 6:03 AM, Kiran wrote:
> If I insert a record from my application using following code :
> db.myschema.cf_question.insert({
> cf_question_type_id:request.payload.type_id,
> cf_question_category_id:request.payload.cat_id,
> lang:request.payload.lang,
> body:request.payload.body
> }
> The above app code inserts the record in the DB, but the respective trigger
> in the database is not triggered hence the "weighted_tsv" columns is empty
> for this record.
>
> But if I insert another record from the postgre's psql, it will insert and
> the respective trigger is working perfectly.
>
> What could be the problem ? Why trigger is not working if I insert from the
> application ? Am I doing anything wrong ?
> Any help would be really really appreciated.

Without knowing what that app code is doing it's impossible to know. Try
turning on logging of all statements (log_statement = ALL) and see what
queries the app is actually running.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
855-TREBLE2 (855-873-2532) mobile: 512-569-9461

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Jim Nasby 2016-09-11 02:32:15 Re: What limits Postgres performance when the whole database lives in cache?
Previous Message Jim Nasby 2016-09-11 02:09:18 Re: 2.5TB Migration from SATA to SSD disks - PostgreSQL 9.2