Skip to content

Update postgres12_end_of_life_notice.mdx #1027

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
mibali wants to merge 1 commit into from
Closed

Update postgres12_end_of_life_notice.mdx #1027

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions docs/admin/postgres12_end_of_life_notice.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -43,3 +43,12 @@ We expect the downtime to last approximately 2.5 hours per TB of code indexed in
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.

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.

### How Can I Check If Reindexing Is Still Running?
Reindexing in Sourcegraph can take several hours, depending on the number of repositories and system resources. While there's no built-in progress tracker, you can check its status using this PostgreSQL query:

```
SELECT * FROM pg_stat_progress_create_index;
```
Look for the `blocks_done` value in the output. Run the query at intervals—if this number increases, reindexing is ongoing. For better readability, enable extended output with `\x` command.
Also note that the reindexing process might take a bit of time reindexing the rockskip table if the reindexing is happening in the code intel DB.

@airamare01 airamare01 Mar 12, 2025 •
edited
Loading

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Line 54/55 doesn't make sense. Could you check what you were trying to communicate here?

@mibali mibali Mar 12, 2025

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@airamare01 The reindexing process applies to all three databases. In Atlassian's case, it specifically occurred in the code intel DB, where we observed that the rockskip table took significantly longer to reindex. That's why I included the caveat.

@enriquegh enriquegh Jul 29, 2025

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@airamare01 @mibali pretty old PR but is this change still needed?

@airamare01 airamare01 Jul 29, 2025

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Deferring to @mibali on this PR.