Opened 3 years ago
Closed 3 years ago
#34489 closed New feature (needsinfo)
feature: Support for PostgreSQL table partitioning
| Reported by: | Anuj Sharma | Owned by: | nobody |
|---|---|---|---|
| Component: | Database layer (models, ORM) | Version: | 4.2 |
| Severity: | Normal | Keywords: | postgresql, table-partitioning, composite primary key |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description (last modified by )
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.
Change History (2)
comment:1 by , 3 years ago
| Description: | modified (diff) |
|---|
comment:2 by , 3 years ago
| Resolution: | → needsinfo |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
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 2008, 2020 and 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
needsinfosince agreement and some high-level design is needed before accepting this as a new feature.