Re: Problem with partitioning
От | Adrian Klaver |
---|---|
Тема | Re: Problem with partitioning |
Дата | |
Msg-id | 111f497e-1437-3d28-a01d-32e8010770c7@aklaver.com обсуждение исходный текст |
Ответ на | Re: Problem with partitioning (JotaComm <jota.comm@gmail.com>) |
Список | pgsql-general |
On 08/03/2016 12:11 PM, JotaComm wrote: > Hello, > > 2016-08-03 15:29 GMT-03:00 Adrian Klaver <adrian.klaver@aklaver.com > <mailto:adrian.klaver@aklaver.com>>: > > On 08/03/2016 11:24 AM, JotaComm wrote: > > > > 2016-08-03 15:20 GMT-03:00 JotaComm <jota.comm@gmail.com > <mailto:jota.comm@gmail.com> > <mailto:jota.comm@gmail.com <mailto:jota.comm@gmail.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.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com> > > > Thank you > > > -- > JotaComm > http://jotacomm.wordpress.com -- Adrian Klaver adrian.klaver@aklaver.com
В списке pgsql-general по дате отправления: