Received: from malur.postgresql.org ([2a02:16a8:dc51::56])
	by arkaria.postgresql.org with esmtps
 (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256)
	(Exim 4.89)
	(envelope-from <pgsql-admin-owner+archive@lists.postgresql.org>)
	id 1fmZeM-00070y-8o
	for pgsql-admin@arkaria.postgresql.org; Mon, 06 Aug 2018 07:09:54 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.89)
	(envelope-from <pgsql-admin-owner+archive@lists.postgresql.org>)
	id 1fmZeK-0000w9-Th
	for pgsql-admin@arkaria.postgresql.org; Mon, 06 Aug 2018 07:09:52 +0000
Received: from makus.postgresql.org ([2001:4800:1501:1::229])
	by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256)
	(Exim 4.89)
	(envelope-from <laurenz.albe@cybertec.at>)
	id 1fmZeK-0000w1-Iy
	for pgsql-admin@lists.postgresql.org; Mon, 06 Aug 2018 07:09:52 +0000
Received: from mx1.mailbox.org ([80.241.60.212])
	by makus.postgresql.org with esmtps (TLS1.2:RSA_AES_256_CBC_SHA1:256)
	(Exim 4.89)
	(envelope-from <laurenz.albe@cybertec.at>)
	id 1fmZeH-0001dQ-Nw
	for pgsql-admin@lists.postgresql.org; Mon, 06 Aug 2018 07:09:51 +0000
Received: from smtp2.mailbox.org (smtp2.mailbox.org [80.241.60.241])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by mx1.mailbox.org (Postfix) with ESMTPS id DA38348721;
	Mon,  6 Aug 2018 09:09:45 +0200 (CEST)
X-Virus-Scanned: amavisd-new at heinlein-support.de
Received: from smtp2.mailbox.org ([80.241.60.241])
	by hefe.heinlein-support.de (hefe.heinlein-support.de [91.198.250.172])
 (amavisd-new, port 10030)
	with ESMTP id Hxy4AISzq1x4; Mon,  6 Aug 2018 09:09:44 +0200 (CEST)
Message-ID: <1533539383.2780.6.camel@cybertec.at>
Subject: Re: PostgreSQL 11 global index
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: Mariel Cherkassky <mariel.cherkassky@gmail.com>, Keith
 <keith@keithf4.com>
Cc: pgsql-admin@lists.postgresql.org
Date: Mon, 06 Aug 2018 09:09:43 +0200
In-Reply-To: 
 <CA+t6e1=eJZotPr_cDh-b8PoYq3XXT3B1zh1-kyr_6AoH11GEkA@mail.gmail.com>
References: 
	<CA+t6e1=uvR0PP_K8FtvMuebzrAofyzsTbMJoQB1pzimTBwfmOA@mail.gmail.com>
	 <CAHw75vtyx-VHPY6tWQSYf52ofDG4D8pCZ6N3E_ZwS5yUmb88nQ@mail.gmail.com>
	 <CA+t6e1=eJZotPr_cDh-b8PoYq3XXT3B1zh1-kyr_6AoH11GEkA@mail.gmail.com>
Organization: Cybertec
Content-Type: text/plain; charset="UTF-8"
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
List-Id: <pgsql-admin.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-admin@lists.postgresql.org>
List-Owner: <mailto:pgsql-admin-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-admin>
Precedence: bulk

Mariel Cherkassky wrote:
> The solution you suggested arent helpfull (both unique index and pg_partman) because I need to
> make sure that in all the partitions I have a specific column that is unique.
> In otherwords one column can have the same value in two different partitions and that
> is the concept of the global index.

There is no way to guarantee uniqueness across partitions in PostgreSQL.

Yours,
Laurenz Albe
-- 
Cybertec | https://www.cybertec-postgresql.com