Planned improvements for Major Database Upgrades
Discussion points for planning improvements to database upgrades
🤖
Auto-Summary Discoto Usage
Points
Discussion points are declared by headings, list items, and single lines that start with the text (case-insensitive)
point:
. For example, the following are all valid points:
#### POINT: This is a point
* point: This is a point
+ Point: This is a point
- pOINT: This is a point
point: This is a **point**
Note that any markdown used in the point text will also be propagated into the topic summaries.
Topics
Topics can be stand-alone and contained within an issuable (epic, issue, MR), or can be inline.
Inline topics are defined by creating a new thread (discussion) where the first line of the first comment is a heading that starts with (case-insensitive)
topic:
. For example, the following are all valid topics:
# Topic: Inline discussion topic 1
## TOPIC: **{+A Green, bolded topic+}**
### tOpIc: Another topic
Quick Actions
Action Description /discuss sub-topic TITLE
Create an issue for a sub-topic. Does not work in epics /discuss link ISSUABLE-LINK
Link an issuable as a child of this discussion
Last updated by this job
-
TOPIC Add development guide for min version changes #826 (comment 570407020)
- update our wording to be that we 'generally' update PG min versions every year. #826 (comment 570407020)
- make the current min version more prominent in the docs #826 (comment 570407020)
- add a process development guide to https://docs.gitlab.com/ee/development/database/index.html that outlines the process for teams to propose a need to change to the min version. #826 (comment 570407020)
- TOPIC Add development guide for min PG version changes #849
- TOPIC Add development guide for min version changes #1128 (closed)
-
TOPIC Reconsider shipping 3 PG Versions in Omnibus #826 (comment 570424415)
- Shipping/supporting 3 would mean we support a PG version for 3 years #826 (comment 570424415)
- Shipping/supporting 3 give our customers 2 years to upgrade #826 (comment 570424415)
- Shipping/supporting 3 allows customer to skip a version during upgrade, so they only need to upgrade every other year #826 (comment 570424415)
- Supporting 3 might limit the features and performance we are able to use in the product on a yearly basis. #826 (comment 570424415)
-
TOPIC Reconsider shipping 3 PG Versions in Omnibus #827
- Shipping/supporting 3 would mean we support a PG version for 3 years #827 (comment 570460239)
- Shipping/supporting 3 give our customers 2 years to upgrade #827 (comment 570460239)
- Shipping/supporting 3 allows customer to skip a version during upgrade, so they only need to upgrade every other year #827 (comment 570460239)
- Supporting 3 might limit the features and performance we are able to use in the product on a yearly basis. #827 (comment 570460239)
- TOPIC Reconsider shipping 3 PG Versions in Omnibus #1129 (closed)
-
TOPIC Support zero downtime upgrades between major Postgres versions #826 (comment 570450682)
- With PG11, logical replication becomes an option, which allows for replication across PG versions. #826 (comment 570450847)
Discoto Settings
---
summary:
max_items: -1
sort_by: created
sort_direction: ascending
See the settings schema for details.
Edited by Lucas Charles