DongHyeonkaandClaude Opus 5
99b689e715
Keycloak commits the login INSERT with synchronous_commit off, so a crash loses whole sessions and not just refresh timestamps. Measured 4 of 153 lost, matching the default wal_writer_delay window. Two injections failed silently first: --grace-period=0 --force lets the container runtime send SIGTERM so PostgreSQL flushes and shuts down cleanly, and SIGKILL to PID 1 from inside its own namespace is ignored by the kernel. Killing a backend makes the postmaster reinitialize, which is a real crash recovery. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
15 lines
807 B
Plaintext
15 lines
807 B
Plaintext
deployment "postgres" successfully rolled out
|
|
|
|
=== crash recovery 가 실행되었는가 (강제 종료의 흔적) ===
|
|
2026-09-04 02:58:41.036 UTC [1] LOG: database system is ready to accept connections
|
|
|
|
=== [설계 확인] 로그인 트랜잭션도 synchronous_commit 을 끄는가 ===
|
|
--- 로그인 트랜잭션 (INSERT 가 있는 것) ---
|
|
2:BEGIN
|
|
5:COMMIT
|
|
6:BEGIN
|
|
9:insert into OFFLINE_USER_SESSION (BROKER_SESSION_ID,CREATED_ON,DATA,LAST_SESSION_REFRESH,REALM_ID,REMEMBER_ME,USER_ID,VERSION,OFFLINE_FLAG,USER_SESSION_ID) values ($1,$2,$3,$4,$5,$6,$7,$8,$9,$10)
|
|
10:insert into OFFLINE_CLIENT_SESSION (DATA,REALM_ID,TIMESTAMP,VERSION,CLIENT_ID,CLIENT_STORAGE_PROVIDER,EXTERNAL_CLIENT_ID,OFFLINE_FLAG,USER_SESSION_ID) values ($1,$2,$3,$4,$5,$6,$7,$8,$9)
|
|
11:SET LOCAL synchronous_commit TO OFF
|
|
12:COMMIT
|