Re: Problem with partitioning

On 08/03/2016 12:11 PM, JotaComm wrote:
> Hello,
>
> 2016-08-03 15:29 GMT-03:00 Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com
> <mailto:adrian(dot)klaver(at)aklaver(dot)com>>:
>
> On 08/03/2016 11:24 AM, JotaComm wrote:
>
>
>
> 2016-08-03 15:20 GMT-03:00 JotaComm <jota(dot)comm(at)gmail(dot)com
> <mailto:jota(dot)comm(at)gmail(dot)com>
> <mailto:jota(dot)comm(at)gmail(dot)com <mailto:jota(dot)comm(at)gmail(dot)com>>>:
>
>
>
> ​When I create a trigger for each child table the trigger
> works very
> well.​
>
>
> ​​
> Without seeing any code this problem is not going to be solved.
>
>
> ​The trigger code:
>
> tg_table_update AFTER UPDATE ON parent_table FOR EACH ROW EXECUTE
> PROCEDURE f_table_update()
>
> CREATE OR REPLACE FUNCTION f_table_update()
>
> RETURNS TRIGGER AS $$
>
> BEGIN
>
> RAISE NOTICE 'update';
>
> UPDATE parent_table SET date=now() WHERE column_id=OLD.column_id;
>
> RETURN NULL;
>
> END;
>
> $$ LANGUAGE PLPGSQL;

In addition to what Tom said:

This is an AFTER UPDATE trigger so the original UPDATE already occurred.
Is it is expected that the OLD.column_id would still be around in the table?

The fact that you are not seeing the RAISE NOTICE 'update' could be
explained by logging settings.

> ​
>
>
>
>
>
> ​Try:
>
> \d+ <tablename> on the relevant table and check/show the
> "Triggers: " section​.
>
> David J.
>
>
> --
> JotaComm
> http://jotacomm.wordpress.com
>
>
>
>
> --
> JotaComm
> http://jotacomm.wordpress.com
>
>
>
> --
> Adrian Klaver
> adrian(dot)klaver(at)aklaver(dot)com <mailto:adrian(dot)klaver(at)aklaver(dot)com>
>
>
> ​Thank you​
>
>
> --
> JotaComm
> http://jotacomm.wordpress.com

--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com