Excerpts from Matteo Beccati's message of lun abr 23 08:49:39 -0300 2012: > Hi, > > I've recently seen a few errors on our continuous integration system > during a test using a badly written partitioning trigger. The function > was basically checking for the existence of the partition table at every > insert and was running a CREATE TABLE IF NOT EXISTS statement in case it > was needed. What baffled me was that the function was exiting with an > ERROR, rather than succeeding with a NOTICE, e.g.:
The question you were asking has already been answered, but I think it's worth pointing out that a partitioned-insert trigger that has to check whether the partition exist beforehand is a lot slower than one that doesn't have to. Our usual suggestion is to create the partitions by some other means, e.g. create a couple months worth of weekly partitions, a couple of months ahead of time, via cron. The insert trigger is then assured that the partition exists, and it can become faster by not having to check. -- Álvaro Herrera <alvhe...@commandprompt.com> The PostgreSQL Company - Command Prompt, Inc. PostgreSQL Replication, Consulting, Custom Development, 24x7 support -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
