How to get around the problem of a small amount of rewriting NAND memory?

Question

PostgreSQL

There is a table with 1 million records, 400 thousand records per day, the table is constantly overwritten by INSERT \ DELETE, the oldest records are deleted, new ones are written in their place.
The question is how to minimize the cost of the Flash memory resource, maybe there are some file systems suitable for Postgres, or maybe somehow set up a table entry, it is important that file after file is written and there are no gaps in memory.
Perhaps there are still some problems when working with Flash, first of all, the opinion of people who have encountered the problem of writing to Flash is of interest.

Answer 1

NAND you would at least name the model of memory or storage device. Maybe you have MLC there and it makes no sense to twitch
More data is needed:
1. RAID?
2. OS
3. The average amount of data per
PS operation has been using only SSD for databases for more than three years

Answer 2

no way - such functions are not taken out of the driver to the user level.
in general, the SSD controller has functions for spraying records by the amount of flash memory for "uniform" memory wear.
True, the quality and functions of the controller are highly dependent on the price.
so it remains only to take not the most deshman drive.