Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1gFnIa-0004i8-15 for pgsql-admin@arkaria.postgresql.org; Thu, 25 Oct 2018 21:36:12 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1gFnIX-0006Cg-Nf for pgsql-admin@arkaria.postgresql.org; Thu, 25 Oct 2018 21:36:09 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1gFnIX-0006CZ-Fv for pgsql-admin@lists.postgresql.org; Thu, 25 Oct 2018 21:36:09 +0000 Received: from n3.nabble.com ([162.255.23.22]) by magus.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1gFnIT-0000Ry-3R for pgsql-admin@postgresql.org; Thu, 25 Oct 2018 21:36:08 +0000 Received: from n3.nabble.com (localhost [127.0.0.1]) by n3.nabble.com (Postfix) with ESMTP id D3897FEBF88F for ; Thu, 25 Oct 2018 14:36:02 -0700 (MST) Date: Thu, 25 Oct 2018 14:36:02 -0700 (MST) From: legrand legrand To: pgsql-admin@postgresql.org Message-ID: <1540503362863-0.post@n3.nabble.com> In-Reply-To: <20181025231655.615d80c2@firost> References: <1540407880009-0.post@n3.nabble.com> <1540501366915-0.post@n3.nabble.com> <20181025231655.615d80c2@firost> Subject: Re: Is there a work around for partition key needed for constraint MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Jehan-Guillaume (ioguix) de Rorthais wrote > On Thu, 25 Oct 2018 14:02:46 -0700 (MST) > > It seems to me you lack some locking to avoid duplicates. cf. my blog post > we > discussed few weeks ago. > > (btw, sorry, I somehow missed your answers on previous thread b/c > holidays). Yes you are right, I forgot to speak about locking, and performance degradation with the number of partitions ... as discussed in the previous thread ;o) -- Sent from: http://www.postgresql-archive.org/PostgreSQL-admin-f2076596.html