Files
neon/docs/rfcs/YYYY-MM-DD-copy-me.md
Alexey Kondratov 8566cad23b chore(docs): Refresh RFC guide to suggest using YYYY-MM-DD prefix (#11252)
## Problem

Serial/numeric IDs lead to collisions, which is not critical but looks
awkward.
Previous discussion:
https://neondb.slack.com/archives/C033A2WE6BZ/p1741891345869979

## Summary of changes

Suggest using the `YYYY-MM-DD` prefix, which i) has less chance of
collision; ii) provides out-of-the-box lexicographic sorting; iii) even
if it collides, it's not a big deal -- just two RFCs have been started
on the same day.

---------

Co-authored-by: Alexander Bayandin <alexander@neon.tech>
2025-03-16 17:17:58 +00:00

558 B

Name

Created on YYYY-MM-DD Implemented on TBD

Summary

Motivation

Non Goals (if relevant)

Impacted components (e.g. pageserver, safekeeper, console, etc)

Proposed implementation

Reliability, failure modes and corner cases (if relevant)

Interaction/Sequence diagram (if relevant)

Scalability (if relevant)

Security implications (if relevant)

Unresolved questions (if relevant)

Alternative implementation (if relevant)

Pros/cons of proposed approaches (if relevant)

Definition of Done (if relevant)