Hi Alvaro,
On 01/05/2012 21:36, Alvaro Herrera wrote:
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
Hi Robert,
On 27/04/2012 20:24, Robert Haas wrote:
The bottom line is that CREATE TABLE IF NOT EXISTS doesn't pretend to
handle concurrency issues any better than regular old CREATE TABLE,
which is to say not very well.
Thanks for the thorough reply. I guessed it was something like that, but
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
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
