From: | github kran <githubkran(at)gmail(dot)com> |
---|---|
To: | Rob Sargent <robjsargent(at)gmail(dot)com> |
Cc: | Ron Johnson <ronljohnsonjr(at)gmail(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Pulling data from Postgres DB table for every 5 seconds. |
Date: | 2019-01-09 18:11:47 |
Message-ID: | CACaZr5TfQrCxNin8ztLOFTshQ8AAJh+Q4uJLYeZyYsCZdwc=-A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Rob - It's a Java based application. We dont have triggers yet on the
table and is trigger a only option in 9.6 version ?.
On Wed, Jan 9, 2019 at 12:01 PM Rob Sargent <robjsargent(at)gmail(dot)com> wrote:
>
> On 1/9/19 10:21 AM, github kran wrote:
>
> Thanks for your reply Rob. Reading the below documentation link says the
> EVENT trigger is only supported for DDL commands. Is it not correct ?.
>
> *1) https://www.postgresql.org/docs/9.6/event-trigger-definition.html
> <https://www.postgresql.org/docs/9.6/event-trigger-definition.html> *
> (An event trigger fires whenever the event with which it is associated
> occurs in the database in which it is defined. Currently, the only
> supported events are ddl_command_start, ddl_command_end, table_rewrite
> and sql_drop. Support for additional events may be added in future
> releases.).
> 2) Doesnt the trigger slow down inserts/update we are doing to the table
> ?. Does it slow down if we are reading the data using the API when we have
> a trigger in place ?.
>
>
> Ah, right you are. Are triggers off the table? You would want to write
> the trigger function in some (trusted?) language with access to the outside
>
From | Date | Subject | |
---|---|---|---|
Next Message | Martín Marqués | 2019-01-09 18:19:46 | Re: postgres operational |
Previous Message | github kran | 2019-01-09 18:10:09 | Re: Pulling data from Postgres DB table for every 5 seconds. |