PostgreSQL

📁 PostgreSQL Hands-on 操作路線 PostgreSQL local lab、connection pool、PITR restore drill、schema migration evidence 與 HA failover 的操作型章節設計

2026-05-18 PostgreSQL Patroni HA：從 leader 失聯到 client 重連的 5 段 failover lifecycle Patroni 把 PostgreSQL HA 拆成 detection / election / promotion / reconfiguration / recovery 五段 lifecycle、每段都有獨立配置跟 failure mode；DCS quorum + watchdog 防 split-brain、async/sync replication 取捨、5 個 production 踩雷、跟 PgBouncer / HAProxy / cert-manager 整合
2026-05-19 PostgreSQL Replication Topology：async / sync / quorum 三模式跟 LSN + replication slot 的三軸組合 PostgreSQL streaming replication 不是「sync 或 async」、是 *durability / latency / consistency* 三軸組合 + LSN-based 進度追蹤 + replication slot 治理。本文走 3 軸取捨模型、async / sync / quorum-based sync 行為對比、LSN + replication slot 機制、配置 step-by-step、5 production 踩雷（standby lag 暴衝 / sync standby 退回 async / orphan replication slot / cascading replication 雪崩 / failover 後 timeline 分歧）、跟 Patroni HA + logical replication 整合
2026-05-19 PostgreSQL Online Schema Change：先用 ALTER 內建特性、不能解才 pg_repack / pg-osc PostgreSQL ALTER TABLE 對多數變更已是 *fast catalog-only*（add column nullable / drop column / 改 default），不必走 ghost table tool。本文走 PG 內建 fast DDL 行為、何時必須走 pg_repack / pg-osc、兩工具機制對比（trigger-based vs WAL-shipping）、配置 step-by-step、5 production 踩雷（lock 升級 / VACUUM FULL 誤用 / pg_repack version mismatch / concurrent index 失敗清理 / generated stored column 不能 online）、跟 MySQL gh-ost / pt-osc sibling 對比
2026-05-19 PostgreSQL Connection Scaling：process-per-connection model 跟為什麼 pooler 是必裝 PG 每個 client connection fork 一個 backend process（不是 thread）、RAM 成本 5-15MB/connection、context switch 跟 fork() cost 在 100+ connection 後線性放大、所以 pooler 不是 *optional optimization* 而是 *production prerequisite*。本文走 process-per-connection model 跟 MySQL thread-per-connection 對比、max_connections + shared_buffers + work_mem 三 GUC 互動、application-side pool vs middleware pool vs RDS Proxy 三層選擇、5 production 踩雷（connection storm / fork() cost 在 burst 流量 / shared_buffers 跟 connection 數壓縮 / double-pool 配置錯誤 / max_connections 設太大反而慢）、跟 PgBouncer config 互補不重複
2026-05-19 PostgreSQL Index Selection：B-tree / GIN / GiST / BRIN / Hash 對應 workload 的決策樹 PG 有 6 種 index method（B-tree / Hash / GIN / GiST / SP-GiST / BRIN）跟 partial / expression / covering 三種變體、不是「都用 B-tree 就好」。每種 index 有自己的 query pattern、儲存代價、write amplification 跟 maintenance 成本。本文走 6 種 index 的適用 workload 對照、決策樹、partial / expression / covering / multi-column 變體、5 production 踩雷（過度 index / partial 條件不對 / B-tree 對 JSON 無效 / BRIN 對非 correlated 資料無效 / multi-column 順序錯）、跟 query-optimization 的 EXPLAIN 互補
2026-05-19 PostgreSQL Citus Distributed：用 extension 把 PG 變成 sharded cluster Citus 是 PG extension、把單機 PG 變成 *coordinator + worker* sharded cluster、保留 PG SQL + 加 distributed table + reference table + columnar storage。本文走 Citus 架構（coordinator / worker / distribution column）、3 種 table type（distributed / reference / local）、配置 step-by-step、5 production 踩雷（distribution column 選錯 / cross-shard transaction / reference table 過大 / colocate 不對齊 / worker failover）、跟 MySQL Vitess sharding sibling 對比
2026-05-19 PostgreSQL SQL Features：PG 早就有的、MySQL 8.0 才補的、PG 仍領先的 PG 在 SQL features 上長期領先 MySQL — CTE / window function / lateral / partial index / FTS / JSONB / GIN index / materialized view 在 PG 早 5-15 年。MySQL 8.0（2018）補多數但 *index / storage / extension* 層仍是 PG 結構優勢。本文整理 PG 早期就有的特性、MySQL 8.0 補的差異、PG 仍領先的、跟 MySQL modern-sql-features sibling 反向視角
2026-05-19 PostgreSQL BDR / Multi-Master：active-active 寫入的 3 種路徑跟 conflict 治理 PG 預設是 single-primary、active-active 多寫入入口需要 *BDR (EDB)* / *pgEdge* / *Bucardo* 等 extension。本文走 3 種 multi-master 方案對比、conflict detection + resolution model、async vs sync 取捨、配置 step-by-step（pgEdge 為主）、5 production 踩雷（last-write-wins data loss / sequence collision / DDL replication / conflict log 治理 / failover 後 timeline 分歧）、跟 MySQL Group Replication sibling 對比
2026-05-19 PostgreSQL Query Optimization：EXPLAIN ANALYZE / pg_hint_plan / auto_explain 三層工具跟 4 個 case PG query 慢的根因常是 *planner 選錯 plan 或 statistics 過時*。本文從 4 個 production case 開場（seq scan vs index / hash vs nested loop / 多 column 統計缺 / parallel query 沒觸發）、走 EXPLAIN / EXPLAIN ANALYZE / auto_explain 三層工具、pg_hint_plan extension 跟 planner GUC 取捨、5 production 踩雷（ANALYZE 過時 / multi-column statistics / cost-base setting 不對齊硬體 / random_page_cost SSD 沒調 / parallel query 配置）、跟 MySQL query-optimization sibling 對比
2026-05-19 PostgreSQL MVCC + Lock Model：為什麼 PG 比 MySQL 少 deadlock、但 vacuum 是別的代價 PG 用 *MVCC-heavy + 少 explicit lock* 的並行控制、跟 MySQL InnoDB 的 *lock-based*（record / gap / next-key）相反。本文走 MVCC 機制（tuple version + xmin/xmax + visibility）、PG 4 種 lock（row-level / table-level / advisory / predicate）、預測 SERIALIZABLE 行為、5 production 踩雷（idle transaction 卡 vacuum / SELECT FOR UPDATE 跨 transaction / advisory lock 沒釋放 / bloat 不是 vacuum 問題 / predicate lock 在 SSI 下 rollback）、跟 MySQL lock-contention sibling 對比
2026-05-19 PostgreSQL JSONB Deep Dive：Binary Storage + GIN Index 為什麼是結構性優勢 PG JSONB（9.4+）是 *binary 儲存的 JSON*、可直接 GIN index、是 PG 在 JSON workload 的結構性優勢、跟 MongoDB / MySQL 8.0 JSON_TABLE 比仍領先。本文走 JSON vs JSONB 差異、GIN index 機制（jsonb_ops vs jsonb_path_ops）、operator + path query、partial JSONB indexing、5 production 踩雷（大 JSONB 跟 TOAST / nested update / index 選錯 op class / jsonb_path_query 跟 jsonb_path_exists 行為差 / partial index 條件搞錯）、何時用 JSONB vs 拆 column
2026-05-19 PostgreSQL Extension Ecosystem：把 PG 變成 vector DB / time-series / sharded 的 plugin 生態 PG 的 extension 機制不只是 plugin、是 *結構性產品線擴張* — pgvector 讓 PG 變 vector DB、TimescaleDB 變 time-series、Citus 變 sharded、PostGIS 變 GIS。本文走 PG extension lifecycle、6 個 production-critical extension（pg_stat_statements / pg_partman / pg_repack / pgvector / TimescaleDB / PostGIS）、5 production 踩雷（extension version 跟 PG version 對齊 / managed PG 限制 / upgrade order / shared_preload_libraries 衝突 / extension 跟 logical replication 互動）、cloud vendor 對 extension 的限制
2026-05-19 PostgreSQL Full-Text Search：tsvector / tsquery / GIN index 跟 pg_trgm fuzzy 三層搜尋 PG 內建 full-text search 用 *tsvector / tsquery / GIN index* 三件組、適合中小規模搜尋（< 100M 文件）；pg_trgm 提供 fuzzy match。本文走 FTS 機制（tsvector 是 lexeme + position 的 vector）、3 種 query（match / ranking / weighted）、multi-language support、跟 pg_trgm fuzzy match 互補、5 production 踩雷（dictionary 選錯 / GIN 跟 GiST 取捨 / ranking 評分權重 / multi-language column 處理 / 何時不該用 PG FTS 改 Elasticsearch）
2026-05-19 PostgreSQL Replication Slot Management：Physical / Logical / Failover Slot 治理 PG replication slot 是 *primary 端的 standby 進度紀錄*、防 WAL premature deletion。但 orphan slot 會吃 disk、failover 後 logical slot 不會自動跟新 primary、是 PG 操作的 hidden complexity。本文走 physical / logical slot 差異、slot lifecycle、failover slot synchronization（PG 17+ 新特性）、orphan slot 治理、5 production 踩雷（orphan slot disk 爆 / logical slot lag / failover 後 slot 丟 / wal_keep_size 跟 slot 衝突 / connection 同時打 slot 數量限制）
2026-05-19 TimescaleDB Deep Dive：Hypertable / Continuous Aggregate / Compression 把 PG 變 Time-Series DB TimescaleDB 是 PG extension（不是 fork）、用 *hypertable* 自動 partition by time、加 *continuous aggregate* 做 incremental materialized view、加 *compression* 對舊 chunk 壓 90%+、把 PG 變成 InfluxDB / Prometheus 級 time-series DB。本文走 hypertable 機制、continuous aggregate 跟普通 MV 差異、compression policy、retention policy、5 production 踩雷（chunk size 不對 / CAGG refresh 落後 / compression 後 update 限制 / hypertable 不能加 FK / TimescaleDB 跟 PG 主版本對齊）、跟 PG 原生 partitioning 對比
2026-05-19 pgvector Deep Dive：HNSW / IVFFlat 取捨跟跟專業 Vector DB 對比 pgvector 是 PG extension、加 *vector* type 跟兩種 ANN index（IVFFlat / HNSW）、把 PG 變成可用 vector DB。本文走 vector type + distance operator、IVFFlat vs HNSW 取捨（build time / recall / memory）、quantization 跟 dimension reduction、5 production 踩雷（dimension 超 2000 限制 / HNSW build 太慢 / IVFFlat 不重建 recall 漂移 / hybrid search 設計 / memory budget）、跟 Pinecone / Weaviate / Milvus 對比的決策框架
2026-05-19 PostGIS Deep Dive：Geometry / Geography 型別、GiST 空間索引跟 ST_* 函式生態 PostGIS 是 PG extension、加 *geometry* / *geography* 型別、GiST 空間索引跟 1000+ ST_* 函式、把 PG 變成功能完整 GIS DB（跟 Oracle Spatial / SQL Server geography 並列）。本文走 geometry vs geography 取捨、SRID 跟投影系統、GiST 空間索引機制、5 production 踩雷（geometry 用錯 SRID / geography 不能用所有 ST_ 函式 / GiST index 不對 ST_DWithin 生效 / cluster on geom 後 BRIN 失效 / EWKB vs WKB 跨工具相容）、GIS workload 的 PG vs 專業 GIS DB 對比
2026-05-18 PostgreSQL autovacuum tuning：為什麼你的 autovacuum 永遠追不上 bloat MVCC 怎麼產生 dead tuple、autovacuum cost-based throttle 為什麼預設保守、per-table tuning 怎麼設、5 個 production 踩雷（cost_limit 太低 / 長 transaction blocks vacuum / anti-wraparound 在 peak / partition vacuum 滿 worker / index bloat 沒處理）、跟 partitioning + monitoring 整合
2026-05-18 PostgreSQL declarative partitioning：partition 不是切表、是讓 planner pruning Declarative partitioning 的真實價值是 query planner pruning + maintenance scope 縮小、不是「把大表切小」；RANGE / LIST / HASH 取捨、partition key 選法、5 個 production 踩雷（key 選錯不 prune / unique 不 enforce 跨 partition / ATTACH 鎖太久 / partition 數爆 / DETACH 不 reclaim 空間）、跟 autovacuum + index 設計整合
2026-05-18 PostgreSQL Logical Replication + Debezium CDC：replication slot × failure × recovery 對照 PostgreSQL logical replication slot 跟 Debezium CDC 的失效模式對照表：slot lag 撐爆 primary disk / schema change 斷流 / 初始 COPY 鎖表 / zombie slot 不釋放 / replay storm 後 offset reset；publication / subscription / pgoutput 配置、跟 Kafka outbox pattern 整合
2026-05-18 PostgreSQL PITR + WAL archiving：從 base backup 到 point-in-time recovery 的完整鏈 Base backup + WAL archive 構成 PITR 的雙軌資料、archive_command + restore_command 配置、用 pgBackRest / WAL-G 替代手寫腳本、5 個 production 踩雷（archive 靜默失敗 / archive lag / 錯誤 target time / base backup 過期未清 / timeline 分歧 recovery 模糊）、跟 Patroni + monitoring 整合
2026-05-19 PostgreSQL major version upgrade (14 → 17)：為什麼這篇不套 5 type migration PostgreSQL major version upgrade 是 *5 type 漏類* 的實證 — source/target 同 vendor、5 維度都 Low 但 *upgrade-specific audit* 是核心；本文結構接近 deep article methodology 的 6-section + 額外 upgrade audit 段；涵蓋 pg_upgrade / logical replication / blue-green 三方法、extension 相容性、5 production 踩雷
2026-05-19 PostgreSQL → Aurora Migration：protocol 相容、operational 重設計 Aurora 號稱 PostgreSQL-compatible 但 operational model 不同（storage decouple / cluster endpoint / instance class / 自家備份）；遷移流程是混合（protocol drop-in + operational phased）、5 個 production 踩雷（extension 不支援 / replication slot 不直通 / autovacuum 行為差 / IAM 認證強制 / cost model 換算）、跟 Patroni / read replica / DR 對位
2026-05-19 PostgreSQL → Aurora DSQL Migration：PG wire-compatible Distributed SQL 的 Paradigm Shift Aurora DSQL（2024-12 re:Invent preview / 2025-05 GA）是 AWS 推的 PG wire-compatible *active-active distributed SQL*、跟 self-managed PG / Aurora PG 不同 paradigm（OCC + snapshot isolation + multi-region strong consistency）。Migration 結構是 *protocol drop-in + paradigm shift*：app SQL 不太改、但 transaction retry / extension 缺位 / 多 region 一致性需重設計。本文走 DSQL vs Aurora PG vs self-managed PG 三軸對比、為什麼遷的三條 driver（global write / operational zero-touch / region resiliency）、Type E phased plan、5 production 踩雷（transaction retry 沒處理 / extension 缺位 / sequence throughput 限制 / Aurora PG 直升 DSQL 不可行 / region failover semantic）、跟 PG → Aurora 跟 PG → CockroachDB 對比
2026-05-19 PostgreSQL → CockroachDB：三維皆 High 的多重歸類 migration PostgreSQL → CockroachDB 是 Schema / Operational / Paradigm 三維皆 High 的 multi-axis migration、實證 [#127](/report/content-structure-by-max-diff-dimension/) 的「多重歸類跟 tie-breaking」規則；主結構走 Type E paradigm shift、Schema 差 + Operational redesign 抽出獨立段；涵蓋 transaction model 重設計、SQL dialect gap、5 個 production 踩雷
2026-05-19 PostgreSQL Partition Redesign：當 monthly partition 越跑越慢 PostgreSQL partition redesign 是 Type F「topology re-layout」第 2 個 dogfood — 從 monthly partition 改 daily / 從 range 改 list / 從單軸改 sub-partition；6 維 audit 皆 Low + topology 軸 High；涵蓋 partition 不平衡偵測、ATTACH/DETACH 線上重劃、5 個 production 踩雷、跟 partition_pruning + autovacuum 整合
2026-05-19 PostgreSQL Multi-Region GDPR Rollout：政策驅動的 migration 屬本 methodology 嗎 PostgreSQL 單 region → multi-region 同時滿足 GDPR EU residency 是 *政策驅動* 兼 *topology 變動* 兼 *operational redesign* 的多軸 migration；驗證 [#128](/report/data-topology-as-audit-dimension/) self-aware limitation 提出的 residency axis 候選 — residency 是 driver 還是獨立 audit 軸；涵蓋 logical replication 配 GDPR / 5 個 production 踩雷 / cross-region cost
2026-05-18 PostgreSQL pgBouncer 配置 + 連線池治理 pgBouncer transaction pooling 配置、跟 application connection pool 的分層、production 故障演練（pool exhaustion / stale connection / DNS failover）跟容量規劃
2026-05-22 Aurora PostgreSQL I/O-Optimized Cost Aurora PostgreSQL Standard 與 I/O-Optimized 的成本模型、I/O 壓力、workload 判斷、遷移與回退條件
2026-05-22 Managed PostgreSQL Comparison RDS PostgreSQL、Aurora PostgreSQL、Cloud SQL、Azure Database for PostgreSQL、Neon、Supabase、Crunchy Bridge 的責任邊界比較
2026-05-22 PostgreSQL Connection Pooler Comparison PostgreSQL PgBouncer、Odyssey、RDS Proxy、application pool 與 transaction pooling 的選型比較
2026-05-22 PostgreSQL Cross-region DR PostgreSQL 跨區災難復原、physical replica、logical replication、backup restore、RPO / RTO 與 failover runbook
2026-05-22 PostgreSQL Developer / DBA Responsibility Split PostgreSQL application developer、DBA、platform team 在 schema、query、migration、backup、incident 與 capacity 的責任分工
2026-05-22 PostgreSQL Logical Decoding Plugins PostgreSQL logical decoding output plugin、pgoutput、wal2json、test_decoding、CDC connector 與 plugin 選型
2026-05-22 PostgreSQL pg_partman Advanced PostgreSQL pg_partman 自動分區、premake、retention、maintenance job、partition migration 與 runbook
2026-05-22 PostgreSQL Security / RLS / Audit Logging PostgreSQL role、grant、Row Level Security、pgAudit、log policy、PII access evidence 與合規路由
2026-05-22 PostgreSQL to YugabyteDB / TiDB Migration PostgreSQL 轉向 YugabyteDB、TiDB 類 distributed SQL 的 compatibility audit、data topology、transaction、cutover 與 rollback
2026-05-22 Specialized PostgreSQL Variants pgvectorscale、Citus、TimescaleDB、PostGIS、AlloyDB、Cosmos DB for PostgreSQL、serverless PG 等 PostgreSQL 變體的選型邊界

#3cx #429 #5w1h #a11y #ab-test #abac #abuse #abuse case #access-control #access-key #access-management #access-pattern #access-revocation #accessibility #ack-deadline #acl #acm #acme #active-active #adb #admin endpoint #adoption #aerospace #agent #agent-architecture #agent-team #agent派發 #aggregation #ai-agent #ai-governance #ai-writing #aider #air-gapped #ai代理人 #ai協作 #ai協作心得 #akamas #alacritty #alarm #alb #alert runbook #alert-fatigue #alerting #alignment #amd #amplitude #analytics #android #anonymization #ansi #anti-pattern #anti-patterns #aof #apfs #api #api-contract #api-design #api-key #apm #app #app-link #apple-silicon #application #applications #arch #arch-linux #architecture #aria #artifact #artifact provenance #artifacts #ascii #assertion #ast #async #asyncio #atexit #atlas #atlassian #att&ck #att&ck evaluations #attack-surface #attention #attribution #audience-awareness #audience-positioning #audit #audit log #audit-dimension #auditable loop #aurora #aurora-dsql #auth0 #authentication #authorization #auto-intercept #auto-recovery #auto-scaling #automation #autovacuum #avro #aws #aws-acm #aws-elasticache #aws-iam #aws-iam-identity-center #aws-kms #aws-s3 #aws-secrets-manager #aws-sqs #aws-sso #aws-waf #axis-candidate #azure #azure-key-vault #azure-rbac #baas #backend #backfill #backpressure #backup #backward-compatible #baseline #bash #basics #batch #batch-writing #bdd #bdr #bear cub #bearer-token #behavior testing #behavioral-detection #benchmark #best-practices #bigquery #binary #bind-address #binlog #biometric #blast radius #blindspot #blog #blog-config #blog心得 #blog維護 #blue team #boot #bootstrap #bottleneck #boundary #branch-protection #brewfile #broker #broot #browser #btop #bubbleup #buffer #buffering #bulkhead #burst-traffic #bus #business #business-analysis #business-case #business-model #buy-vs-build #c-extension #ca #cache #cache invalidation #caelestia #caffeine #canary #capability #capability-upgrade #capacity #capacity-mode #capacity-planning #capital #cardinality #cards-skills #case-analysis #case-driven #case-first #case-first-workflow #case-study #cassandra #catppuccin #cd #cdc #cdn #cert-manager #cffi #chain-of-thought #change healthcare #change-feed #change-streams #changelog #channel #chaos #chaos engineering #chapter-structure #chart #checklist #checkout #checkov #checkpoint #chezmoi #chronicle #ci #ci-cd #ci/cd #cidr #cilium-tetragon #circuit-breaker #cisa #citation #citrix bleed #citus #class #classification #claude #claude code #clean architecture #cli #client #client-server #client-side #clock-drift #cloud #cloud-cost #cloud-data-policy #cloud-iam #cloud-llm #cloud-logging #cloud-managed #cloud-monitoring #cloud-security #cloud-sql #cloudflare #cloudflare-access #cloudflare-waf #cloudhealth #cloudhsm #cloudtrail #cloudwatch #cluster #cnapp #cockroach-cloud #cockroachdb #code-generation #code-quality #code-smell #codex #coding #coding-agent #cognitive-load #cohort #collaboration #collaborative-filtering #collapse #collection-strategy #collector #comfyui #commercial #communication #comparison #completeness #compliance #compositional-writing #compositor #compute #concurrency #conditional-write #config rollout #conflict-resolution #conftest #connection #connection-pool #connection-pooling #consensus #consistency #consolidation #constants #constrained-decoding #constraint-design #consul #consumer #consumer-group #consumer-lag #consumption #container #container-scan #containment #content-based #content-design #context #context-engineering #context-management #context-window #continue-dev #contract-test #control failure #control handoff #control map #control mapping #control pattern #control plane #control validation #convention #conversion #copywriting #coroutine #correlation id #cors #cosmosdb #cost #cost-governance #cost-management #cost-model #cost-optimization #cost-thinking #courses #coverage #cpu-offload #cpython #cqrs #crashlytics #credential #credential-rotation #cross-cloud #cross-link #cross-module #cross-platform #cross-vendor #crowdstrike-falcon-cs #csf #cspm #css #ctypes #cuda #customer-identity #d1 #d3fend #dart #dashboard #data classification #data exfiltration #data flow #data inconsistency #data lifecycle #data plane #data-architecture #data-boundary #data-consistency #data-control #data-engineering #data-integrity #data-minimization #data-pipeline #data-protection #data-quality #data-repair #data-residency #data-security #data-shape #data-types #data-warehouse #database #datadog #datadog-security #dax #db-document #db-kv #db-oltp #dblab #ddd #ddl #ddos #dead-code #dead-letter-topic #deadlock #debezium #debounce #debug #debuggability #debugging #decision #decision dialogue #decision log #decision-tree #decoding #decorator #dedup #deep-article #deep-link #default-design #defender pressure #defense #defense vocabulary #definition #degradation #degraded-mode #deletion evidence #delivery #delivery-mode-selection #delta #denormalization #dependabot #dependency #dependency-injection #deployment #deployment-platform #descriptor #design #design-pattern #design-patterns #design-tradeoff #desktop #desktop-environment #detection #detection coverage #detection engineering #detection-rule #devcontainer #developer #development-environment #devops #diagnosis #diagnostic endpoint #diffusion #digest #disaster-recovery #discrete-gpu #disk #disk-space #distributed #distributed-counter #distributed-lock #distributed-sql #distributed-systems #dlp #dlq #dns #docker #docker-swarm #document #document-model #document-store #documentation #dom #domain設計 #dotfile #downtime #dr #dragonflydb #draining #drawer #drift #drop-in #drop-off #dry #dsl #duplicate delivery #durability #dynamic-credential #dynamodb #e2e #ebpf #ecs #edge #edge exposure #edge-cache #editor #edr #eks #elastic-cloud #elastic-security #elastic-stack #elasticache #embedded #embedding #emulator #encryption #enforcement-design #entra-id #entry-point #environment #error #error-handling #error-message #error-recovery #error-storm #error-tracking #escape #etcd #eval #evals #evaluation #event #event-classification #event-contract #event-delivery #event-design #event-driven #event-enumeration #event-format #event-loop #event-peak #eviction #evidence #evidence package #evolution #exactly-once #exception #execution #exercise design #expectation #explain #exponential-backoff #export #extension #external-consistency #failover #failure patterns #failure-mode #falco #fallback #fallback-design #false confidence #false-alarm #false-negative #false-positive #false-trigger #fargate #fastly #fastly-ngwaf #fault-tolerance #fde #feature-flag #feature-tier #federation #federation trust #field cases #file-manager #filter #fine-tuning #fingerprint #finops #firebase #firestore #fixture #flaky #flaky test #flash-sale-spike #fleet #flow-control #flush #flutter #font #fontconfig #form #foundations #frame-coverage #framework #framing #free-threading #freezed #freshness #frontend #frontend-with-playwright #frontmatter #ftp #full-stack #full-text-search #function #function-calling #funnel #fuse.js #fuzzing #fzf #ga4 #game day #gate #gate-fallback #gatekeeper #gatling #gc #gcp #gdpr #gemma #generics #geoserver #getter #getx #gguf #ghas #gil #gis #git #gitguardian #github #github-actions #github-advanced-security #gitleaks #gitui #global #global-database #global-edge #global-sql #global-tables #gnuplot #go #go-advanced #goaccess #goldmark #google-cloud-iam #google-cloud-kms #google-dlp #google-pubsub #google-secret-manager #google-security-operations #googlesql #goreplay #gorouter #goroutine #governance #gpu #gql #graceful-shutdown #gradle #grafana #grafana-cloud #grafana-oncall #grammar #grep #group-replication #grouping #grype #gsi #gsm #gtid #gtk #gtm #gui #ha #handover #hands-on #happy-path #harbor #hardware #harlequin #harness #hashicorp #hashicorp-vault #hatch #health #health-check #heatwave #helpdesk #hig #high-availability #high-cardinality #high-frequency-write #higher-order-function #hlc #homebrew #honeycomb #hook #hook系統 #horizontal-scaling #hot-partition #hsm #htap #htop #http #https #hugo #human-ai-collaboration #human-in-the-loop #hypothesis-testing #hyprland #hyprlock #i18n #iac #iac-scan #iam #ide #ide-integration #idempotency #identifier #identity #idle timeout #ilm #image #ime #immuta #impact scope #implementation #import #imports #improvement #in-context-learning #incident #incident cases #incident decision log #incident evidence #incident learning #incident severity #incident workflow #incident-response #index #inference #inference-optimization #inference-server #information architecture #information-protection #information-theory #infra #infrastructure #ingestion #inheritance #innodb #innodb-cluster #input #install #installation #installer #instruction-following #instrumentation #integration #integration-test #intel #interface #interleaved-tables #internal endpoint #invalidation #io-threads #ios #iredis #isolate #isolation #isr #ivanti #javascript #jenkins #jetstream #jmeter #journalctl #js #json #json-schema #jsonb #jsonl #judgment #k6 #k9s #kafka #kando #kaskade #kent beck #key #keyboard #keycloak #keydb #kitty #kms #knowledge #knowledge gardening #knowledge routing #knowledge-card #knowledge-cards #knowledge-work #kubernetes #kv #kv-cache #kyverno #lacework #lambda #language-design #laravel #late #latency #layout #lazygit #lazysql #leaf-node #lectures #legacy #letsencrypt #library #lifecycle #linear-algebra #linearizability #lint #linux #litestream #liveness #llama-cpp #llm #llm-as-judge #lm-studio #load balancer contract #load shedding #load-balancer #load-balancing #load-test #load-testing #local-first #local-llm #local-llm-services #local-vs-cloud #locality #lock #locking #locust #log #log-compaction #log-pipeline #log-schema #logging #logical-decoding #logical-replication #logs #loki #long-context #long-term-storage #lora #loss #low-latency-sustained #lsi #lsp #lua #m-trends #mac #macos #major-upgrade #mako #managed #managed-service #management plane #mandiant #markdown #market-dynamics #marketing #mass exploitation #material-design #materials #math #math-foundations #maturity #maturity model #maxwell #mcp #mdm #memcached #memory #memory-budget #mental-model #mermaid #mesh-vpn #message-queue #meta-commentary #metaclass #metadata #metadata-lock #metaprogramming #methodology #methodology-selection #metric #metrics #mfa #mft #mgm #microservice #microsoft-purview #middleware #migration #migration-playbook #mimir #mindset #minisearch #mitigation #mitre #mixpanel #ml-detection #mlx #moat #mobile #mock #model-architecture #model-behavior #model-family #model-selection #model-trust #module #modules #moe #mongodb #mongodb-api #monitoring #monorepo #mosh #motivation #moveit #mq-stream #msk #mtls #mtp #mttr #multi-account #multi-agent #multi-axis #multi-cluster #multi-dc #multi-gpu #multi-master #multi-model #multi-pass #multi-region #multi-round-review #multi-source #multi-tenant #multicore #multilingual #multimedia #multimodal #multiplexer #multiprocessing #mutationobserver #mvcc #mysql #naming #nat #nats #navigation #neovim #network #network-exposure #network-partition #networking #neural-network #new-relic #nexus #nginx #ngxtop #nist #nix #node #noise #non-technical #nosql #notes #ntp #numerical-precision #nvidia #observability #offline #oidc #okta #olap #ollama #oltp #on-call #onboarding #online-ddl #oomkill #oop #opa #open-source #open-webui #opentelemetry #opentofu #operational-hybrid #operations #opinionated-software #ops-loop #optimization #optimizer #orchestration #orchestrator #ordering-key #organization #organizations #os #oss #otlp #outbox #over-match #override #owasp #ownership #paas #package #package-management #package-manager #packaging #pacman #page-shield #pagefind #palo-alto #pam #pane #paradigm #paradigm-shift #parallel #parallel-dispatch #parca #parser #partition #partition-key #partitioning #path #pathlib #patroni #pattern #peak-estimation #peak-event #pel #performance #permission #persistence #pg-partman #pgbouncer #pgcli #pgvector #phased-translation #philosophy #php #pii #pipeline #piper #pitr #pki #planetscale #planning #platform #playbook #playwright #plotext #poetry #policy control #policy-as-code #pooler #pos #post-incident review #postgis #postgresql #postgresql-dialect #posts #pprof #pragma #pre-commit #precision #predictable-peak #predictive-scaling #presence #pretraining #preview #principles #priority #prisma-cloud #privacera #privacy #probability #probe #problem cards #process #process-writing #production #production-validation #professional sources #profiling #prometheus #prompt-cache #prompt-engineering #prompt-injection #prompting #promql #property-graph #protocol #protocol-integration #provenance #provisioning #proxy #proxysql #pub-sub #push #push-pop #push-pull #pyo3 #pyproject #pyroscope #python #python-advanced #qlora #quality #quantization #query #query-boundary #query-optimization #queue #quickshell #quickstart #quorum #quorum-queue #quota #qwen #rabbitmq #raft #rag #rainfrog #ram #ranger #ransomware #rate-limit #rate-limiting #rba #rdb #rds #rds-proxy #reachability #read-preference #read-replica #read-write #readability #reader-experience #reader-first #readiness #reading #realtime #reasoning #rebalance #recall #recommendation #reconciliation #recording-rules #recovery #red-team #redaction #redis #redis-compatibility #redis-streams #redundancy #refactor #refactoring #registry #rego #regulated #release #release freeze #release gate #release governance #release-tracking #reliability #remote #remote-access #remote-config #remote-write #replay #replica #replication #replication-slot #report #repository-adapter #representativeness #reproducibility #required-checks #requirement-protocol #requirements #rerun #reserved-instance #resharding #residency #resilience #resiliency matrix #resource #resource-limit #resource-planning #resource-pool #response routing #responsive design #retention #retrieval #retrofit #retrospective #retry #retry-loop #reverse-proxy #review #review-design #review-process #review-timing #review機制 #rfm #rhythm #rice #ripgrep #risk #risk acceptance #risk governance #risk input #risk routing #rls #roblox #rocm #roi #rollback #rollback rehearsal #rollback strategy #rollout #root-cause #root-cause-analysis #rotation #route53 #router #routing #rpo #rsync #rto #ru-sizing #rule-codification #rule-engine #rum #runbook #runtime #runtime config #runtime-detection #runzonedguarded #rust #s3 #saas #safety #sampling #sanctum #sans #sast #saturation #sbom #sca #scaffold #scale #scaling #scenario #schema #schema-design #schema-diff #schema-evolution #schema-migration #schema-registry #scope #scope-management #scp #screen-state #screen-state-test #screenshot #sdk #sdk-design #search #secret #secret-management #secret-scanning #secrets #security #security control #security design #security materials #security operations #security references #security testing #security-group #security-rules #segmentation #select #selector #self-hosted #self-review #semantics #semver #sensitive-data #sensor #sentinel #sentry #serializable #server #serverless #service design #service discovery #service registry #service-locator #service-mesh #service-selection #service-worker #session #session invalidation #session-recording #session-replay #session-token #setup #severity #shard-key #sharded #sharding #shared controls #shared-storage #shell #shortcode #siem #sigma #signal #signal quality #signing #signing key #simulation #simulator #single-table-design #skill #skills #slab-allocator #sliding-window #slo #slow-log #snapshot #snapshot-listener #snowflake #snyk #soar #sociable unit tests #social engineering #source #source-of-truth #spa #spanner #spanner-graph #spatial #specification #speculative-decoding #speech-to-text #spiffe #spire #split-brain #splunk #spot-instance #spurious-failure #spurious-warning #sql #sql-api #sql-features #sqlite #sre #ssh #ssot #stable-diffusion #stakeholder #stakeholder mapping #stanford-cs230 #state #state-machine #state-management #state-matrix #stateful #stateless #static stability #static-site #statistics #status page #statusline #stdlib #steady state #sticky session #storage #stored-procedure #storm-0558 #stow #strategy #stream #streaming-replication #streams #struct #structured-output #subnet #supercluster #supply-chain #support workflow #surge #survival-goals #sustained-growth #svelte #syft #synapse-link #sync #systemd #tab-bar #table-locality #tabletop #tagging #tailscale #tailscale-ssh #takeover #tdd #tdd流程 #teaching-structure #team #technical-writing #telemetry #telemetry-pipeline #teleport #template-abuse #tempo #termgraph #terminal #terminology #terraform #test #test-data #test-design #test-time-compute #testcontainers #testing #tflint #tfsec #theme #theoretical-foundations #theory #threading #threat intelligence #threat model #threat-informed defense #threat-modeling #throughput #ticket #ticket整合 #ticket管理 #ticket系統 #ticket追蹤 #tier #tiered-storage #tig #til #tiling #time-machine #time-series #timeout #timescaledb #timeseries #timestamp #timezone #tls #tmux #toc #toil #token #token revocation #token scope #token-bucket #tokenization #tone #tool-design #tool-use #tooling #tools #topic-drift #topology #touch #traceability #tracing #tradeoffs #traffic #traffic-management #traffic-mirroring #traffic-replay #training #transaction #transformer #transition #translation #transport #triage #trigger #tripwire #trivy #troubleshooting #truetime #ttl #tts #tty #ttyd #tui #tuning #tunnel #turso #two-tier #type-a #type-b #type-c #type-e #type-f #type-hints #type-i-error #type-ii-error #type-system #typedef #typing #uefi #ui #ui-test #unit-economics #unittest #universal-link #update #upgrade #uptime #usql #utm #ux #ux-design #vacuum #validation #valkey #valuenotifier #vantage #variants #vault #vector-database #vector-search #vegeta #vendor #vendor-article #vendor-mapping #vendor-selection #verification #version-management #version-upgrade #versioning #vertical-saas #vertical-slice #viewmodel #visibility-timeout #vision #visual #visual-regression #vitess #vlm #vm #vpc #vram #vscode #vulnerability response #waf #wal #wal-archive #waybar #wayland #web #websocket #wezterm #whisper #widget #widget-test #window-manager #windows #wiz #wofi #work-log #workflow #workload #workload-identity #worklog #wrap #wrap-decision #write-back #write-sharding #writing #writing-methodology #writing-spec #writing-workflow #x11 #xclaim #xz utils #yabai #yagni #yaml #yazi #yozefu #zellij #zero-trust #zettelkasten #zone #zsh #ztna #並行分析 #並行評估 #事件處理 #事件驅動 #事後檢討 #事故圍堵 #事故後檢討 #事故案例 #事故決策紀錄 #事故等級 #任務拆分 #任務派發 #任務管理 #供應鏈 #供應鏈完整性 #依賴方向 #停機 #健康檢查 #備份刪除 #允許清單 #內容分類 #內部端點 #全局分析 #全方位評估 #函式設計 #分層架構 #利害關係人地圖 #前端開發 #前置知識卡片 #功能旗標 #卡片盒筆記 #原則 #原子任務 #可靠性 #吞吐量 #告警處置手冊 #命名規範 #品質改善 #品質標準 #品質檢查 #品質管理 #商業分析 #問題覺察 #問題評估 #單元測試 #單字 #回滾演練 #回滾策略 #國際化 #圖表 #地區化 #執行期設定 #外部組件 #多視角分析 #契約 #字源 #學習筆記 #完成定義 #容器 #容錯切換 #寫作 #寫作方法論 #寫作規範 #專案管理 #對話協議 #導航 #就緒檢查 #工作日誌 #工作流 #工作流程 #工作準則 #工具 #工具技巧 #工具設計 #工具評估 #工具鏈 #工程實踐 #工程方法論 #工程筆記 #平均修復時間 #建議追蹤 #影響半徑 #影響範圍 #復原時間目標 #復原點目標 #快取失效策略 #技術債務 #技術寫作 #技術文件 #技術選型 #抽象層 #拉丁文 #持續改善 #指標 #授權 #排空 #探針 #搜尋 #效率工具 #敏捷 #敏捷開發 #教學 #教材結構 #教材設計 #整合測試 #文件撰寫 #文件系統 #文件規範 #文件設計 #文檔架構 #方法論 #會話失效 #服務發現 #服務註冊 #架構升級 #架構合規 #架構設計 #框架設計 #機密管理 #權杖撤銷 #決策呈現 #決策框架 #決策樹 #決策記錄 #治理例外 #流程 #流程圖 #流程設計 #測試 #測試驅動 #測試驅動開發 #溝通 #漸進式遷移 #版本企劃 #物件導向設計 #狀態機 #狀態頁 #發布 #發布凍結 #發布關卡 #知識傳遞 #知識卡 #知識卡片 #知識基礎建設 #知識管理 #程式品質 #程式碼品質 #程式碼審查 #程式碼操作 #程式碼設計 #程式設計 #稽核日誌 #穩態 #管理平面 #管理端點 #系統化開發 #系統思考 #系統遷移 #素材庫 #統計 #經驗分享 #經驗收集 #聯邦信任 #背壓控制 #自動化 #自檢機制 #英文單字 #處置手冊 #術語 #訊息管理 #訊號偵測 #訊號關聯 #設定發布 #設計驅動 #診斷端點 #註解規範 #認知負擔 #語意搜尋 #證據包 #議題hub #讀者旅程 #負載削峰 #負載平衡協議 #負載平衡器 #資安 #資安治理 #資安演練 #資料不一致 #資料保護 #資料分級 #資料生命週期 #資源限制 #資訊架構 #跨語言開發 #跨領域 #身分驗證 #軟體架構 #速率限制 #逾時 #選型訪談 #重構 #重複手動工作 #重複投遞 #重評估觸發器 #錯誤處理 #錯誤預防 #鍵盤 #開發原則 #開發工具 #開發流程 #開發策略 #閒置逾時 #降級 #除錯 #階段管理 #雜項 #需求澄清 #需求管理 #靜態網站 #響應式設計 #風險評估 #首頁 #驗收 #驗收條件 #驗收流程 #黏性會話