Date: Wed, 21 Nov 2018 01:09:57 -0700 (MST)
From: legrand legrand <legrand_legrand@hotmail.com>
To: pgsql-admin@postgresql.org
Message-ID: <1542787797239-0.post@n3.nabble.com>
In-Reply-To: 
 <CAHw75vvsSCGxWSZMj0cBN-brVVwDZ-N1kvnZ7Bx=F-jpMNbP4g@mail.gmail.com>
References: 
 <CACBZq4xNCVEsCSnV_vhOQULtcwUnHpji+=eyw2sE2=_2V2n3Mg@mail.gmail.com>
 <CAHw75vvsSCGxWSZMj0cBN-brVVwDZ-N1kvnZ7Bx=F-jpMNbP4g@mail.gmail.com>
Subject: Re: Trigger to create automated range partition table
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Precedence: bulk

I confirm: This is not working now

for pg10 see
https://www.postgresql-archive.org/BUG-15437-Segfault-during-insert-into-declarative-partitioned-table-with-a-trigger-creating-partition-td6054925.html

this kind of trigger is even not supported in pg11
postgres=# CREATE TRIGGER check_pkey BEFORE INSERT ON tabpart
postgres-#      FOR EACH ROW EXECUTE PROCEDURE public.f_check_pkey();
ERROR:  "tabpart" is a partitioned table
DETAIL:  Partitioned tables cannot have BEFORE / FOR EACH ROW triggers.

There are many development works regarding this
see all threads about ATTACH/DETACH PARTITION CONCURRENTLY
for example

Today the only solution is to create those partitions before the first
INSERT statement ;o(

Regards
PAscal


--
Sent from: http://www.postgresql-archive.org/PostgreSQL-admin-f2076596.html