Timeline for Creating and dropping partition in PostgreSQL "on the fly"?
Current License: CC BY-SA 4.0
5 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Sep 17, 2020 at 18:48 | comment | added | ScienceKitten | Application knows that new partition do not exist before creating and partition for deleting exists before deleting. | |
Sep 17, 2020 at 13:34 | comment | added | Laurenz Albe | With "backend" you probably mean the application. Does the application know which partitions exist or does it have to query the database for every row that it wants to insert? The latter would probably not make for good performance, the former (caching that information) poses the problem tat the cache might get stale. Perhaps catching an error, creating the partition if necessary and retrying is the most performant option. | |
Sep 17, 2020 at 13:32 | history | edited | Laurenz Albe | CC BY-SA 4.0 |
deleted 175 characters in body
|
Sep 17, 2020 at 12:55 | comment | added | ScienceKitten |
We do not use creating partition by BEFORE INSERT trigger. We create or drop section on backend after user start creating or deleting forecast on frontend of our web-application.
|
|
Sep 17, 2020 at 2:58 | history | answered | Laurenz Albe | CC BY-SA 4.0 |