You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/admin/postgres12_end_of_life_notice.mdx
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,7 +14,7 @@ The impact to you depends on how you currently manage your Sourcegraph databases
14
14
### Built-in Databases
15
15
If you are using Sourcegraph's released Postgres images, these images will be updated to Postgres 16 as part of the Sourcegraph 5.10 release (expected for November 25th, 2024) and all near term subsequent releases. With this update, Sourcegraph will experience a longer-than-average downtime at the time of the upgrade to version 5.10 or beyond. This downtime is proportional to the amount of code indexed in your instance, and can range from approximately 15 minutes to a couple of hours. The downtime will only occur at the first upgrade to version 5.10 or beyond, and not during any subsequent upgrades.
16
16
17
-
We strongly recommend that you consider this downtime prior to upgrading to ensure minimal disruption to your users. We also strongly recommend creating a backup of your database before the upgrade process.
17
+
We strongly recommend that you consider this downtime prior to upgrading to ensure minimal disruption to your users. We also strongly recommend creating a backup of your database before the upgrade process, as an interruption to the upgrade process could lead to database corruption.
18
18
19
19
### External Databases
20
20
If you are using externally managed databases for your Sourcegraph instance, you will need to manually upgrade the version of Postgres you are using to Postgres 16. For the Sourcegraph version that will be released on January 15, 2025 and subsequent versions, Sourcegraph will no longer run on any version of Postgres lower than Postgres 16, and you will not be able to upgrade your instance to any of those Sourcegraph versions unless that minimum required version of Postgres is met.
@@ -42,4 +42,4 @@ We expect the downtime to last approximately 2.5 hours per TB of code indexed in
42
42
### If I'm using external databases with Sourcegraph, how do I upgrade my version of Postgres? Can I upgrade Postgres independently of a Sourcegraph upgrade?
43
43
Upgrading your Postgres version is highly dependent on your specific situation. If you have a separate team managing this database, reach out to them to understand their practices. And, as always, feel free to reach out to Sourcegraph to assist you.
44
44
45
-
When using external databases, you can upgrade your Postgres version at any time, either alongside a Sourcegraph upgrade or independently of it. We encourage you to do so as soon as it's convenient for you.
45
+
When using external databases, you can upgrade your Postgres version at any time, either alongside a Sourcegraph upgrade or independently of it. We encourage you to do so as soon as it's convenient for you.
Copy file name to clipboardExpand all lines: docs/technical-changelog.mdx
+44-1Lines changed: 44 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,9 +4,52 @@ This page documents all notable changes to Sourcegraph. For more detailed change
4
4
5
5
{/* CHANGELOG_START */}
6
6
7
+
# 5.10 Patch 1
8
+
9
+
> Warning: This release updates the database container images from Postgres 12 to Postgres 16, and begins using Wolfi based images. See our [Postgres 12 end of life](https://sourcegraph.com/docs/admin/postgres12_end_of_life_notice#postgres-12-end-of-life) notice!
10
+
>
11
+
> Warning: `automatic` and migrator `upgrade` command will not work for this release, please upgrade to a 5.9 version and conduct a standard upgrade using migrator's default `up` command!
12
+
>
13
+
> Also be sure to check your deployment type's [upgrade notes](http://sourcegraph.com/docs/admin/updates#instance-specific-procedures)!
- remove 5.10 deprecation dates on out of band migrations [#1996](https://github.com/sourcegraph/sourcegraph/pull/1996)
30
+
- We are removing the deprecation dates on out of band migrations which deprecated in 5.10. This is to unblock MVU and autoupgrades which are encountering a bug with deprecated out of band migrations. Backport f654dcc9200e2dda2deddc8f98bcd972e6a873fd from #1995
31
+
32
+
#### Search
33
+
34
+
- disable zoekt go-git optimization by default [#2051](https://github.com/sourcegraph/sourcegraph/pull/2051)
35
+
- Disabled an indexed search optimization which would skip files accidentally (`ZOEKT_DISABLE_GOGIT_OPTIMIZATION=true`). Backport 34ada948bdcee3d75499c98f4db5c32986943e88 from #2050
36
+
37
+
### Reverts
38
+
39
+
There were no reverts for this release
40
+
41
+
### Uncategorized
42
+
43
+
#### Others
44
+
45
+
- [Backport 5.10.x] oob: Actually run for all tenants [#1994](https://github.com/sourcegraph/sourcegraph/pull/1994)
> Warning: This release updates the database container images from postgres 12 to postres 16, and begins using wolfi based images. See our [postgres 12 end of life](https://sourcegraph.com/docs/admin/postgres12_end_of_life_notice#postgres-12-end-of-life) notice!
52
+
> Warning: This release updates the database container images from Postgres 12 to Postgres 16, and begins using Wolfi based images. See our [postgres 12 end of life](https://sourcegraph.com/docs/admin/postgres12_end_of_life_notice#postgres-12-end-of-life) notice!
10
53
>
11
54
> Warning: `automatic` and migrator `upgrade` command will not work for this release, please upgrade to a 5.9 version and conduct a standard upgrade using migrator's default `up` command!
0 commit comments