Issues

• Arrow_Fdwのメタデータ処理改善

  heterodb/pg-strom#1067 · Filter by author kaigai opened on Oct 12, 2026
  1

• gpucache: トリガのオプション変更とTRUNCATEの後、SELECTが間欠的に"GPU-Cache not found"で失敗する

  bug
  heterodb/pg-strom#1066 · Filter by author 0-kaz opened on Oct 1, 2026

• gpucache: gpucache_info() が不正なJSONを返す

  bug
  heterodb/pg-strom#1065 · Filter by author 0-kaz opened on Oct 1, 2026

• gpucache: gpucache_apply_redo() を実行しても未適用の更新ログが適用されない

  bug
  heterodb/pg-strom#1064 · Filter by author 0-kaz opened on Oct 1, 2026

• gpucache: 共有メモリのハッシュスロットの範囲外アクセスにより、更新のハングやGPU Serviceのクラッシュが起きる

  bugin progress
  heterodb/pg-strom#1063 · Filter by author 0-kaz opened on Oct 1, 2026
  1

  

• You may not create foreign tables with too many columns

  heterodb/pg-strom#1062 · Filter by author anarazel opened on Sep 30, 2026

• arrow_index: GPUが複数ある環境で GpuPreAgg の actual rows が期待値と一致しない

  heterodb/pg-strom#1061 · Filter by author 0-kaz opened on Sep 27, 2026

• KDSバッファへの書き込みでnitems/usageがオーバーラップする事がある。

  heterodb/pg-strom#1060 · Filter by author kaigai opened on Sep 14, 2026

• [BUG] 並列GpuScanでCUDA_ERROR_MISALIGNED_ADDRESS発生後、後続クエリがハングする

  heterodb/pg-strom#1059 · Filter by author 0-kaz opened on Sep 13, 2026

• [Performance] Selectivity misestimation overselects GpuJoin for a.x = 42

  heterodb/pg-strom#1055 · Filter by author gdbpbt opened on Aug 17, 2026

• [Performance] Enabling PG-Strom regresses a selective indexed self-join by 23x

  heterodb/pg-strom#1054 · Filter by author gdbpbt opened on Aug 16, 2026

• PostgreSQL 19でLEFT JOINとHAVING集約を含むクエリをGPU実行すると「Aggref found in non-Agg plan node」エラーになる

  wait for confirmation
  heterodb/pg-strom#1052 · Filter by author 0-kaz opened on Aug 15, 2026
  3

• GPU-Cacheの段階的Compaction

  heterodb/pg-strom#1049 · Filter by author kaigai opened on Aug 13, 2026

• query1 UNION [ALL] query2の置き換え

  heterodb/pg-strom#1048 · Filter by author kaigai opened on Aug 13, 2026
  1

• vcf2arrowのエラーメッセージ

  heterodb/pg-strom#1042 · Filter by author kaigai opened on Jul 2, 2026

• GROUP BY queries hang indefinitely when the default compute_60 gpu-architecture is used on an H100 (should be compute_90)

  heterodb/pg-strom#1041 · Filter by author ckeenan-seekr opened on Jun 23, 2026

• SIGSEGV in pgstromGpuCacheShutdown() when a GpuCache scan runs in a non-parallel sub-plan (NULL gcache_fetch_count)

  heterodb/pg-strom#1039 · Filter by author a-hirota opened on Jun 22, 2026

• GPU-Cacheよ再び

  heterodb/pg-strom#1038 · Filter by author kaigai opened on Jun 17, 2026

• [備忘録] ARM 統合型GPUへの対応を検討

  future action
  heterodb/pg-strom#1037 · Filter by author kaigai opened on Jun 9, 2026

• [備忘録] Parquet Cacheの耐障害性

  heterodb/pg-strom#1036 · Filter by author kaigai opened on Jun 5, 2026
  2

• [備忘録] SQLの実行時間の可視化

  future action
  heterodb/pg-strom#1035 · Filter by author kaigai opened on Jun 5, 2026

• Arrow_FdwでS3からの直接読み出し

  heterodb/pg-strom#1033 · Filter by author kaigai opened on May 29, 2026
  4

• strom_io_vector の fchunk_id が32bit

  heterodb/pg-strom#1032 · Filter by author kaigai opened on May 25, 2026

• CustomScan (GpuXXX) with parallel_aware=false under Gather node

  heterodb/pg-strom#1027 · Filter by author kaigai opened on May 1, 2026
  2

• gpu_cache test hang in PG18: pgstrom.gpucache_apply_redo('t') does not return

  heterodb/pg-strom#1020 · Filter by author 0-kaz opened on Apr 7, 2026
  1