Hi !
I would like to thank you all for your detailed answers and explanations.
I would give "partitioning" a try, by creating a dedicated new partition
table, and insert a (big enough) extract of the source data in it.
You are right, the best would be to try in real life !
Best wishes
Kimaidou
On 3/5/24 13:47, Marc Millas wrote:
> Salut Kimaidou,
> why not a partitioned table with the department a partitioning Key ?
> each year just detach the obsolete data, department by
> department (ie.detach the partition, almost instantaneous) and drop or keep
> the obsolete data.
> No delete, quite
Salut Kimaidou,
why not a partitioned table with the department a partitioning Key ?
each year just detach the obsolete data, department by
department (ie.detach the partition, almost instantaneous) and drop or keep
the obsolete data.
No delete, quite easy to maintain. For each global index, Postgr
Hi list,
In France, the total number of cadastral parcels is around 10 000 000
The data can be heavy, because each parcel stores a geometry (PostGIS
geometry data type inside a geom column).
Indexes must be created to increase performance of day-to-day requests:
* GIST index on geom for spatial
