Timeline for Dealing with out-of-range values on a PARTITION BY RANGE
Current License: CC BY-SA 4.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 15, 2018 at 16:02 | vote | accept | NotAnAuthor | ||
| May 15, 2018 at 3:13 | answer | added | Erwin Brandstetter | timeline score: 7 | |
| May 14, 2018 at 17:25 | comment | added | NotAnAuthor | Thanks @ErwinBrandstetter. Do you know of a way to get the lower and upper bounds of the range by query? | |
| May 14, 2018 at 15:42 | comment | added | Erwin Brandstetter | My first idea would be to create future partitions ahead of time. Enough to cover eventualities. (And keep doing so as time advances.) Empty tables are patient and very modest creatures, they'll wait until needed and won't bother you. | |
| May 14, 2018 at 13:51 | history | undeleted | NotAnAuthor | ||
| May 11, 2018 at 19:57 | history | deleted | NotAnAuthor | via Vote | |
| May 11, 2018 at 18:22 | history | edited | NotAnAuthor | CC BY-SA 4.0 |
edited title
|
| May 11, 2018 at 18:18 | review | First posts | |||
| May 11, 2018 at 19:24 | |||||
| May 11, 2018 at 18:15 | history | asked | NotAnAuthor | CC BY-SA 4.0 |