On Fri, Mar 24, 2017 at 5:36 PM, Thomas Munro <thomas.mu...@enterprisedb.com> wrote: > On Fri, Mar 24, 2017 at 1:14 PM, Thomas Munro > <thomas.mu...@enterprisedb.com> wrote: >> If that's fixed and the permissions question can be waved away by >> saying it's the same as the per-row situation, my only other comment >> would be a bikeshed issue: Enr isn't a great name for a struct. > > One more thought: should this be allowed? > > postgres=# create table mytab (i int) partition by list (i); > CREATE TABLE > postgres=# create table mytab1 partition of mytab for values in (42); > CREATE TABLE > postgres=# create function my_trigger_function() returns trigger as $$ > begin end; $$ language plpgsql; > CREATE FUNCTION > postgres=# create trigger my_trigger after update on mytab referencing > old table as my_old for each statement execute procedure > my_trigger_function(); > CREATE TRIGGER
On second thoughts, that's actually arguably a bug in committed code. What do you think about the attached patch? -- Thomas Munro http://www.enterprisedb.com
no-transition-tables-for-partitioned-tables.patch
Description: Binary data
-- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
