[Django] #34489: feature: Support for PostgreSQL table partitioning

[Django]

#34489: feature: Support for PostgreSQL table partitioning
-------------------------------------+-------------------------------------
Reporter: Anuj | Owner: nobody
Sharma |
Type: New | Status: new
feature |
Component: Database | Version: 4.2
layer (models, ORM) | Keywords: postgresql, table-
Severity: Normal | partitioning, composite primary key
Triage Stage: | Has patch: 0
Unreviewed |
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------+-------------------------------------
Postgresql added support for table partitioning from 10.x; currently, it
is on 15.x.

Django should add support for PostgreSQL table partitioning so that the
database engine can be used efficiently.

Currently, I can only see one library supporting partitioning (django-
postgres-extra)[https://django-postgres-
extra.readthedocs.io/en/latest/table_partitioning.html]. Still, it also
has limitations in migration because Django does not support composite
primary key, which is the key requirement for the Postgres table
partitioning.

--
Ticket URL: <https://code.djangoproject.com/ticket/34489>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

[Django]

#34489: feature: Support for PostgreSQL table partitioning
-------------------------------------+-------------------------------------

Reporter: Anuj Sharma | Owner: nobody
Type: New feature | Status: new
Component: Database layer | Version: 4.2
(models, ORM) |
Severity: Normal | Resolution:
Keywords: postgresql, table- | Triage Stage:
partitioning, composite primary | Unreviewed
key |
Has patch: 0 | Needs documentation: 0

Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------

Description changed by Anuj Sharma:

Old description:

> Postgresql added support for table partitioning from 10.x; currently, it
> is on 15.x.
>
> Django should add support for PostgreSQL table partitioning so that the
> database engine can be used efficiently.
>
> Currently, I can only see one library supporting partitioning (django-
> postgres-extra)[https://django-postgres-
> extra.readthedocs.io/en/latest/table_partitioning.html]. Still, it also
> has limitations in migration because Django does not support composite
> primary key, which is the key requirement for the Postgres table
> partitioning.

New description:

Postgresql added support for table partitioning from 10.x; currently, it
is on 15.x.

Django should add support for PostgreSQL table partitioning so that the
database engine can be used efficiently.

Currently, I can only see one library supporting partitioning [django-
postgres-extra](https://django-postgres-
extra.readthedocs.io/en/latest/table_partitioning.html). Still, it also

has limitations in migration because Django does not support composite
primary key, which is the key requirement for the Postgres table
partitioning.

--

--
Ticket URL: <https://code.djangoproject.com/ticket/34489#comment:1>

[Django]

#34489: feature: Support for PostgreSQL table partitioning
-------------------------------------+-------------------------------------
Reporter: Anuj Sharma | Owner: nobody

Type: New feature | Status: closed

Component: Database layer | Version: 4.2
(models, ORM) |

Severity: Normal | Resolution: needsinfo

Keywords: postgresql, table- | Triage Stage:
partitioning, composite primary | Unreviewed
key |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------

Changes (by Natalia Bidart):

* status: new => closed
* resolution: => needsinfo

Comment:

Composite primary keys feature is being tracked in ticket #373 and in
MultipleColumnPrimaryKeys, and it has been discussed in the developer
mailing list multiple times (at least in [[https://groups.google.com/g
/django-developers/c/SyNwoGUtkTU/m/_RNCGnLKRCMJ|2008]],
[[https://groups.google.com/g/django-
developers/c/OeA7PcK87to/m/oAY7epAgBwAJ|2020]] and
[[https://groups.google.com/g/django-developer|2021]]).

I think that the specific feature that is being requested should be first
discussed and agreed on the developers mailing list, since I couldn't find
an existing post or ticket about it. Setting this ticket as `needsinfo`
since agreement and some high-level design is needed before accepting this
as a new feature.

--
Ticket URL: <https://code.djangoproject.com/ticket/34489#comment:2>