Re: Postgres 11: Table Partitioning and Primary Keys
Michael Paquier <[email protected]>
| Newsgroups | gmane.comp.db.postgresql.devel.documentation,gmane.comp.db.postgresql.devel.general |
|---|---|
| Message-ID | <[email protected]> |
On Tue, Jul 09, 2019 at 03:34:48PM +0900, Michael Paquier wrote: > Looking closely at the code in DefineIndex() (and as Rajkumar has > mentioned upthread for unique constraints) this can happen for primary > keys, unique constraints and exclusion constraints. So we had better > mention all three of them. I am not sure that we need to be explicit > about the uniqueness part though, let's say the following: > "When defining a primary key, a unique constraint or an exclusion > constraint on a partitioned table, all the columns present in the > constraint definition must be included in the partition key." Let's try again that (that's a long day..): "When defining a primary key, a unique constraint or an exclusion constraint on a partitioned table, all the columns present in the partition key must be included in the constraint definition." -- Michael
signature.asc
(application/pgp-signature, 833 B)
-----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEG72nH6vTowiyblFKnvQgOdbyQH0FAl0kOXwACgkQnvQgOdby QH0LhQ//VbAt6JUGuSBXBnwMW85j9pInASy4YXofLurZ5Kf1yWac9uAViG7vkZKF qOC6Z4A1Ncap3wSjHHBYvYWvDOrfBUqxolQsaU3sdutISDkbBTz8rwwT8/WWB1Oa +LzRG5opAygtmuvVQNbR5j1p+ZkPnN14exafiu+WtZEGd21ciiFBrBIOWXiJzZKs cX9uvQAnbfWL6L+DKRntAgGvaZDYLHBoPe+DhjGqrBO3xE5Xh7jkwLjza7wDtJpi ZZTh2FvPwTqX80+IIB9znkpvjjLoRzLPwkN4A/ud6Z0q+x7+j9nv5PWxJga2xi0Q lSvvx1NNp5phzFAzOr07jXCG8EyuZr9FO/RU1uPXtsmaBzUI6uWqhr3LXXQfuBd5 yXBqqe2uxBOzb+qJRB2G8AcmAUoNNEIpr2jWm6RHFsdaGJbAS4acRwiLNje4VQR0 OzzX3iXIbULSAiEl8dgl+yi/zLjypghMWmiDykezlYPLhabpeBICFvjIUi9gq5O0 FdZIzZAjugwWdkUPAn96hx+1w+YfznVVF3QRjbbDHVwVlXqpYvwa3p3rfnJqFZPN ukanDrp11DVx7mqh8wK3fQvDIabJ9dcgVk0XrJW4h7LIDE0frVEibD/acIqEBqIs HwxkbouOFFRFB8ztQGqjha54Fn5D+pnPAVIIEKyZ7HQdFoEZsj8= =6Tkh -----END PGP SIGNATURE-----