<feed xmlns='http://www.w3.org/2005/Atom'>
<title>postgresql.git/src/backend/lib, branch master</title>
<subtitle>This is the main PostgreSQL git repository.</subtitle>
<id>http://git.postgresql.org/cgit/postgresql.git/atom?h=master</id>
<link rel='self' href='http://git.postgresql.org/cgit/postgresql.git/atom?h=master'/>
<link rel='alternate' type='text/html' href='http://git.postgresql.org/cgit/postgresql.git/'/>
<updated>2026-08-17T07:15:45Z</updated>
<entry>
<title>Use safer allocation routines in more places of the tree</title>
<updated>2026-08-17T07:15:45Z</updated>
<author>
<name>Michael Paquier</name>
</author>
<published>2026-08-17T07:15:45Z</published>
<link rel='alternate' type='text/html' href='http://git.postgresql.org/cgit/postgresql.git/commit/?id=51c43a5dbd86ad8461544e54c00bd9f487abfacd'/>
<id>urn:sha1:51c43a5dbd86ad8461544e54c00bd9f487abfacd</id>
<content type='text'>
This is part of a more global effort to modernize the code tree with
safer allocation functions, which offer more protection in terms of:
- stronger type safety guarantees
- size overflow checks, particulary for arrays.

This set of updates includes allocation changes based on
palloc_object(), palloc_array() and repalloc_array().  This work is
similar to 1b105f9472bd, expanding more the new APIs in the tree in an
incremental fashion.

Author: Tristan Partin &lt;tristan@partin.io&gt;
Discussion: https://postgr.es/m/DKJB5887LGX9.359DV1UMZ1URK@partin.io
</content>
</entry>
<entry>
<title>Add dshash_get_dsa_area(), able to retrieve the DSA area of a dshash table</title>
<updated>2026-08-03T11:05:23Z</updated>
<author>
<name>Michael Paquier</name>
</author>
<published>2026-08-03T11:05:23Z</published>
<link rel='alternate' type='text/html' href='http://git.postgresql.org/cgit/postgresql.git/commit/?id=762e329e83f2194969a6ea859ddd08361a18ac98'/>
<id>urn:sha1:762e329e83f2194969a6ea859ddd08361a18ac98</id>
<content type='text'>
Code using GetNamedDSHash() to retrieve a dshash table may also want to
limit its size, but there is actually no easy way to do so because the
dsa_area of a hash table is hidden within dshash.c.

This commit adds dshash_get_dsa_area() to close the gap, which returns
the dsa_area for a given dshash_table.  The DSA area retrieved can then
be passed to dsa_set_size_limit(), to limit its size.  This accessor
routine also opens the door for allocating additional objects in the
same DSA area as a hash table, which may be useful for some.

Author: Sami Imseih &lt;samimseih@gmail.com&gt;
Discussion: https://postgr.es/m/CAA5RZ0tKfCVqFnMZtavM42H63ha2Haf_C4mbJNWqkaW30cPW1w@mail.gmail.com
</content>
</entry>
<entry>
<title>Fix for loop variables</title>
<updated>2026-07-11T12:39:15Z</updated>
<author>
<name>Peter Eisentraut</name>
</author>
<published>2026-07-11T12:38:33Z</published>
<link rel='alternate' type='text/html' href='http://git.postgresql.org/cgit/postgresql.git/commit/?id=e615da8cb21b3745456da45197fa5dc620f19dab'/>
<id>urn:sha1:e615da8cb21b3745456da45197fa5dc620f19dab</id>
<content type='text'>
A number of for loops used loop variables that did not match the type
of the end condition.  This could lead to wraparound or
signed/unsigned mismatches.  Probably none of these are a problem in
practice, but it's fragile code.

Reviewed-by: Tom Lane &lt;tgl@sss.pgh.pa.us&gt;
Discussion: https://www.postgresql.org/message-id/flat/d639aede-209f-412b-927a-d38d4848b370%40eisentraut.org
</content>
</entry>
<entry>
<title>Pre-beta mechanical code beautification, step 1: run pgindent.</title>
<updated>2026-05-13T14:34:17Z</updated>
<author>
<name>Tom Lane</name>
</author>
<published>2026-05-13T14:34:17Z</published>
<link rel='alternate' type='text/html' href='http://git.postgresql.org/cgit/postgresql.git/commit/?id=020794ee42a3413b416898e7931a8a3a5b43e9ab'/>
<id>urn:sha1:020794ee42a3413b416898e7931a8a3a5b43e9ab</id>
<content type='text'>
Update typedefs.list from the buildfarm, and run pgindent.
The changes from the new typedefs list are pretty minimal,
since we'd been pretty good (not perfect) about updating
typedefs.list by hand.  But the pgindent behavior changes
installed by a3e6beba6, b518ba4af, and 60f9467c3 add up
to make this a relatively sizable diff.
</content>
</entry>
<entry>
<title>Fix a set of typos and grammar issues across the tree</title>
<updated>2026-04-21T05:46:22Z</updated>
<author>
<name>Michael Paquier</name>
</author>
<published>2026-04-21T05:46:22Z</published>
<link rel='alternate' type='text/html' href='http://git.postgresql.org/cgit/postgresql.git/commit/?id=d3bba041543593eb5341683107d899734dc8e73e'/>
<id>urn:sha1:d3bba041543593eb5341683107d899734dc8e73e</id>
<content type='text'>
This batch is similar to 462fe0ff6215 and addresses a variety of code
style issues, including grammar mistakes, typos, inconsistent variable
names in function declarations, and incorrect function names in comments
and documentation.  These fixes have accumulated on the community
mailing lists since the commit mentioned above.

Notably, Alexander Lakhin previously submitted a patch identifying many
of the trivial typos and grammar issues that had been reported on
pgsql-hackers.  His patch covered a somewhat large portion of the issues
addressed here, though not all of them.

The documentation changes only affect HEAD.
</content>
</entry>
<entry>
<title>dshash: Make it possible to suppress out of memory errors</title>
<updated>2026-03-19T15:51:17Z</updated>
<author>
<name>Robert Haas</name>
</author>
<published>2026-03-19T15:51:17Z</published>
<link rel='alternate' type='text/html' href='http://git.postgresql.org/cgit/postgresql.git/commit/?id=6f0738ddec85b416e7186e3099be70a3420bf3ea'/>
<id>urn:sha1:6f0738ddec85b416e7186e3099be70a3420bf3ea</id>
<content type='text'>
Introduce dshash_find_or_insert_extended, which is just like
dshash_find_or_insert except that it takes a flags argument.
Currently, the only supported flag is DSHASH_INSERT_NO_OOM, but
I have chosen to use an integer rather than a boolean in case we
end up with more flags in the future.

Reviewed-by: Chao Li &lt;li.evan.chao@gmail.com&gt;
Reviewed-by: Sami Imseih &lt;samimseih@gmail.com&gt;
Discussion: http://postgr.es/m/CA+TgmoaJwUukUZGu7_yL74oMTQQz2=zqucMhF9+9xBmSC5us1w@mail.gmail.com
</content>
</entry>
<entry>
<title>Remove #include &lt;math.h&gt; where not needed</title>
<updated>2026-01-15T18:09:47Z</updated>
<author>
<name>Álvaro Herrera</name>
</author>
<published>2026-01-15T18:09:47Z</published>
<link rel='alternate' type='text/html' href='http://git.postgresql.org/cgit/postgresql.git/commit/?id=35e3fae738e63f4154814dd51d3806d8d8b7b673'/>
<id>urn:sha1:35e3fae738e63f4154814dd51d3806d8d8b7b673</id>
<content type='text'>
Liujinyang reported the one in binaryheap.c, I then found and analyzed
the rest.

For future patches, we require git archaelogical analysis before we
accept patches of this nature.

Co-authored-by: liujinyang &lt;21043272@qq.com&gt;
Co-authored-by: Álvaro Herrera &lt;alvherre@kurilemu.de&gt;
Discussion: https://postgr.es/m/tencent_6B302BFCAF6F010E00AB5C2C0ECB7AA3F205@qq.com
</content>
</entry>
<entry>
<title>Update copyright for 2026</title>
<updated>2026-01-01T18:24:10Z</updated>
<author>
<name>Bruce Momjian</name>
</author>
<published>2026-01-01T18:24:10Z</published>
<link rel='alternate' type='text/html' href='http://git.postgresql.org/cgit/postgresql.git/commit/?id=451c43974f8e199097d97624a4952ad0973cea61'/>
<id>urn:sha1:451c43974f8e199097d97624a4952ad0973cea61</id>
<content type='text'>
Backpatch-through: 14
</content>
</entry>
<entry>
<title>Use palloc_object() and palloc_array() in backend code</title>
<updated>2025-12-09T22:36:46Z</updated>
<author>
<name>Michael Paquier</name>
</author>
<published>2025-12-09T22:36:46Z</published>
<link rel='alternate' type='text/html' href='http://git.postgresql.org/cgit/postgresql.git/commit/?id=1b105f9472bdb9a68f709778afafb494997267bd'/>
<id>urn:sha1:1b105f9472bdb9a68f709778afafb494997267bd</id>
<content type='text'>
The idea is to encourage more the use of these new routines across the
tree, as these offer stronger type safety guarantees than palloc().
This batch of changes includes most of the trivial changes suggested by
the author for src/backend/.

A total of 334 files are updated here.  Among these files, 48 of them
have their build change slightly; these are caused by line number
changes as the new allocation formulas are simpler, shaving around 100
lines of code in total.

Similar work has been done in 0c3c5c3b06a3 and 31d3847a37be.

Author: David Geier &lt;geidav.pg@gmail.com&gt;
Discussion: https://postgr.es/m/ad0748d4-3080-436e-b0bc-ac8f86a3466a@gmail.com
</content>
</entry>
<entry>
<title>Add some missing #include &lt;limits.h&gt;.</title>
<updated>2025-11-13T09:56:08Z</updated>
<author>
<name>Thomas Munro</name>
</author>
<published>2025-11-13T09:56:08Z</published>
<link rel='alternate' type='text/html' href='http://git.postgresql.org/cgit/postgresql.git/commit/?id=017249b828880073140a3e4cc13858804b4418de'/>
<id>urn:sha1:017249b828880073140a3e4cc13858804b4418de</id>
<content type='text'>
These files relied on transitive inclusion via port/atomics.h for
constants CHAR_BIT and INT_MAX.

Reviewed-by: Heikki Linnakangas &lt;hlinnaka@iki.fi&gt;
Discussion: https://postgr.es/m/536409d2-c9df-4ef3-808d-1ffc3182868c@iki.fi
</content>
</entry>
</feed>
