Skip to content

PostgreSQL contributions

What is already in the PostgreSQL core, with the credit in the commit.

The extensions on this site run on top of PostgreSQL; this is work inside PostgreSQL. Every line below is a commit in the official repository that credits Manuel Reyes Bravo in its message, and opens on git.postgresql.org.

credited commits
22
Author
5
Co-authored-by
1
Reviewed-by
12
Tested-by
2
Reported-by
2

Counted on 2026-11-14 in the public repository, by searching for the email in each commit message. A commit applied to several branches counts once. On the PostgreSQL lists he signs as "Manu".

The weightiest one

A new index on a system catalog.

Applied to master by Álvaro Herrera on 2026-11-12.

Author 2026-11-12

Index pg_constraint.confrelid to avoid seqscans

A new index on the pg_constraint catalog, over confrelid. Since NOT NULL constraints got their own row in that catalog, several operations scanned all of it and became slow; the commit message names pg_upgrade and ATTACH/DETACH PARTITION. The index avoids that scan.

Author
Manuel Reyes Bravo
Reported-by
Bernhard Wonisch, David Rowley
Suggested-by
Tom Lane
Reviewed-by
Álvaro Herrera
Committer
Álvaro Herrera

Files: src/include/catalog/pg_constraint.hsrc/backend/commands/tablecmds.csrc/backend/catalog/heap.csrc/include/catalog/catversion.h

Open the commit · b0496e30830

Written

As author and co-author.

What each one fixes, summarized from the commit message. The subject is verbatim.

  1. Author 2026-10-27
    Count the last block of the validation scan in a concurrent index build

    In CREATE INDEX CONCURRENTLY and REINDEX CONCURRENTLY, the progress view did not count the last block of the validation phase, so blocks_done never reached blocks_total.

    committer: Michael Paquier · 99ea4a55270

  2. Author 2026-10-17
    Avoid unnecessary end-of-recovery barrier waits

    Promoting a standby could wait indefinitely on a backend that could not process the end-of-recovery barrier, for example one blocked sending data to a client that stopped reading. Promotion now finishes without that wait. Authorship shared with Fujii Masao.

    committer: Fujii Masao · 239c4d30699

  3. Author 2026-10-06
    Fix three blips with progress reporting data (heap and GIN)

    Three wrong values in the progress views: the last key counted twice in a parallel GIN index build, a tuple counter that was not incremented, and an off-by-one in blocks_done during an index build. The message says Manu reported two and Michael Paquier found the third while reviewing his patches.

    committer: Michael Paquier · 3be29d9346d

  4. Author 2026-09-18
    Don't quote the relation name twice in EXCEPT clause errors.

    In the errors of the publication EXCEPT clause, a schema or table name that needed quoting came out quoted twice.

    committer: Amit Kapila · 926627bf902

  5. Co-authored-by 2026-10-06
    Fix ADD PRIMARY KEY after dropping and re-adding a column

    Dropping a NOT NULL column, adding another with the same name and making it the primary key in a single ALTER TABLE could fail with "primary key column ... is not marked NOT NULL". The author is Fujii Masao; Manu is credited as Co-authored-by.

    committer: Fujii Masao · 5659e549ade

Reviewed, tested and reported

The work on other people’s patches.

Reviewed-by means having reviewed the patch before it went in; Tested-by, having tested it; Reported-by, having reported the problem the commit fixes.

  1. 2026-11-05 Reviewed-by
    SQL/JSON: Fix NULL result leakage in JSON_VALUE() RETURNING json/jsonb committer: Amit Langote · 627c4df3b73
  2. 2026-11-04 Reviewed-by
    Fix Memoize to correctly use clause's input collation committer: David Rowley · 35273454065
  3. 2026-11-02 Reviewed-by
    Add REPACK progress phases for logical decoding setup. committer: Masahiko Sawada · 51ae21aa313
  4. 2026-11-02 Reviewed-by
    Fix WAL summary boundary checks for incremental backups. committer: Fujii Masao · f549ecd2660
  5. 2026-10-29 Reviewed-by
    Fix eager aggregation below volatile join clauses committer: Richard Guo · 27c844034f8
  6. 2026-10-20 Reviewed-by
    contrib/intarray: always parse query_int integers as decimal. committer: Tom Lane · ccfe1db5a8a
  7. 2026-10-16 Reviewed-by
    doc: Correct the description of server behavior after an OOM kill committer: Fujii Masao · 14904052e65
  8. 2026-10-14 Reviewed-by
    pg_basebackup: Report correct size estimate for incremental backups committer: Fujii Masao · 4c674b952a6
  9. 2026-10-01 Reviewed-by
    Refresh autovacuum costs while waiting for parallel workers. committer: Masahiko Sawada · 4a80214270a
  10. 2026-09-28 Reviewed-by
    Turn "check" into assertion committer: Álvaro Herrera · 2b1d52b1979
  11. 2026-09-23 Reviewed-by
    doc: Clarify phase descriptions of pg_stat_progress_repack. committer: Masahiko Sawada · 8a2beb5f15f
  12. 2026-09-17 Reviewed-by
    Distinguish publication exclusions in object addresses. committer: Amit Kapila · 94670ba6d56
  13. 2026-11-05 Tested-by
    SQL/JSON: Fix ON EMPTY/ERROR state leakage on NULL input committer: Amit Langote · ee7cfb99a34
  14. 2026-11-02 Tested-by
    Make parallel vacuum processes share the cost limit. committer: Masahiko Sawada · 8628df8891a
  15. 2026-09-17 Reported-by
    Further post-revert cleanup after online checksums committer: Daniel Gustafsson · 6b0760a10a3
  16. 2026-09-16 Reported-by
    Fix online checksums revert leftovers committer: Daniel Gustafsson · 4a9a6c5a69c

Acknowledgments

In the PostgreSQL 19 release notes.

The Acknowledgments section of the PostgreSQL 19 release notes lists the people who contributed to that release. "Manuel Reyes Bravo" is on that list, in the official documentation on postgresql.org.

Open the PostgreSQL 19 release notes

Who applied them

In PostgreSQL only a committer can apply a change, after reviewing it. The ones on this list were applied by:

  • Fujii Masao 5
  • Masahiko Sawada 4
  • Álvaro Herrera 2
  • Amit Kapila 2
  • Amit Langote 2
  • Daniel Gustafsson 2
  • Michael Paquier 2
  • David Rowley 1
  • Richard Guo 1
  • Tom Lane 1

How to read this page

What counts and what does not.

Who is Manuel Reyes Bravo
  • 01

    Only what is committed to an official branch (master or a REL_*_STABLE) counts. The credit is the one the committer wrote in the message.

  • 02

    Work under discussion on pgsql-hackers or registered in a commitfest does not count: until it is applied, it is not here.

  • 03

    The hash in each row is from one of the branches that hold the commit. If it was applied to several, the row appears once.

  • 04

    The count can be repeated: clone the repository and search for the email with git log --grep.

Contact

Write to us. We will get back to you.

Enterprise edition, security audit or agent-to-database integration: one email with two lines about your case is enough. We answer in English and Spanish.

Email

manu@latamflows.com

A person reads the email. If you would rather write directly, the address is above.

Or tell us here

We only use this to reply to you. No lists, no newsletters.

Who is behind this

Manuel Reyes Bravo

The seven extensions, the image and the contributions to PostgreSQL core are signed by Manuel Reyes Bravo, from Chile. To talk code, repositories or the PostgreSQL lists, his personal email:

Personal email

manuelreyesbravo@gmail.com

Also through GitHub issues: pg_agent_gate/issues

Try it Talk