Kuropen on Nostr: If your database is not using C or POSIX for its collation setting (which you can ...
If your database is not using C or POSIX for its collation setting (which you can check with SELECT datcollate FROM pg_database WHERE datname = current_database();), your indexes might be inconsistent if you ever ran with a version of glibc prior to 2.28 and did not immediately reindex your databases after updating to glibc 2.28 or newer.
https://docs.joinmastodon.org/admin/troubleshooting/index-corruption/libcのバージョンでDBのインデックス不整合が起きるのか…
Published at
2024-09-01 06:41:41Event JSON
{
"id": "0d561d07acc638c9f960c1f6b62a8009afa952b1cfc91abf78109055ea5255e3",
"pubkey": "d6f00fb730b8f9437f983965da45ca598ee9d6afba696b4d04f2a4abeb0ac5b5",
"created_at": 1725172901,
"kind": 1,
"tags": [
[
"proxy",
"https://mi.kuropen.org/notes/9xmrprs2ku",
"activitypub"
]
],
"content": "If your database is not using C or POSIX for its collation setting (which you can check with SELECT datcollate FROM pg_database WHERE datname = current_database();), your indexes might be inconsistent if you ever ran with a version of glibc prior to 2.28 and did not immediately reindex your databases after updating to glibc 2.28 or newer.https://docs.joinmastodon.org/admin/troubleshooting/index-corruption/\n\nlibcのバージョンでDBのインデックス不整合が起きるのか…",
"sig": "f9cfdea9b6ce905b1d9c2a679cf6f33633c085fcadd8a825bd3305411bf294afb0153e7bf0e5aeca23181c00018ee2b1d9e81e853109e2d692e056ef32ac1a52"
}
