CI history

  • #20Jul 20, 2022Japin Li
  • #19Jul 20, 2022Alvaro Herrera
  • #16Jul 20, 2022tanghy.fnst@fujitsu.com
  • #11Jul 20, 2022Michael Paquier
  • #10Jul 20, 2022tanghy.fnst@fujitsu.com
  • #4Jul 19, 2022Japin Li
  • #2Jul 19, 2022Japin Li
  • #1Jul 19, 2022tanghy.fnst@fujitsu.com
  • #20Jul 20, 2022
    v5-0001-fix-the-memory-leak-in-psql-describe.patch
    pg14-v5-0001-fix-the-memory-leak-in-psql-describe.patch
    + 1 more
  • #19Jul 20, 2022
    0001-More-goto-error_return-in-describe.c.patch
  • #16Jul 20, 2022
    v5-0001-fix-the-memory-leak-in-psql-describe.patch
  • #11Jul 20, 2022
    v4-0001-fix-the-memory-leak-in-psql-describe.patch
  • #10Jul 20, 2022
    v3-0001-fix-the-memory-leak-in-psql-describe.patch
  • #4Jul 19, 2022
    v2-0001-Fix-the-memory-leak-in-psql-describe.patch
  • #2Jul 19, 2022
    v1-0001-Fix-the-memory-leak-in-psql-describe.patch
  • #1Jul 19, 2022
    v1-0001-fix-the-memory-leak-in-validateSQLNamePattern.patch

Beta feature Hackorum builds and tests every patch posted to the lists, not only commitfest submissions. This is Hackorum's own CI rather than the PostgreSQL project's, and it is still under testing - please report anything that looks wrong.

won't retrysuccessCI history

You can run a PostgreSQL built from this patch straight from Docker, with no checkout and no build:

docker run --rm -p 5432:5432 ghcr.io/hackorum-dev/postgres-patch:t46251
psql -h localhost -U postgres

Built from patchset v20 (message #20), July 28, 2026 at 02:20 AM.

Every patchset is also pushed to a branch of our PostgreSQL fork, so you can check out the same tree CI built. Without a PostgreSQL checkout:

git clone --branch t46251_20 https://github.com/hackorum-dev/postgres.git

In a checkout you already have, add the fork once:

git remote add hackorum https://github.com/hackorum-dev/postgres.git

then, for this patchset and every later one:

git fetch hackorum t46251_20 && git checkout t46251_20

Patchset v20 (message #20) is on t46251_20