postgres-github.git / log / commits on 2026-04-12
23:39 e3e26d04bd52 Fix unlikely overflow bug in bms_next_member()
David Rowley <drowley@postgresql.org>
23:39 e3e26d04bd52 Fix unlikely overflow bug in bms_next_member()
David Rowley <drowley@postgresql.org>
23:39 e3e26d04bd52 Fix unlikely overflow bug in bms_next_member()
David Rowley <drowley@postgresql.org>
23:39 e3e26d04bd52 Fix unlikely overflow bug in bms_next_member()
David Rowley <drowley@postgresql.org>
23:39 e3e26d04bd52 Fix unlikely overflow bug in bms_next_member()
David Rowley <drowley@postgresql.org>
23:39 e3e26d04bd52 Fix unlikely overflow bug in bms_next_member()
David Rowley <drowley@postgresql.org>
23:39 e3e26d04bd52 Fix unlikely overflow bug in bms_next_member()
David Rowley <drowley@postgresql.org>
23:39 e3e26d04bd52 Fix unlikely overflow bug in bms_next_member()
David Rowley <drowley@postgresql.org>
23:39 e3e26d04bd52 Fix unlikely overflow bug in bms_next_member()
David Rowley <drowley@postgresql.org>
23:39 e3e26d04bd52 Fix unlikely overflow bug in bms_next_member()
David Rowley <drowley@postgresql.org>
23:39 e3e26d04bd52 Fix unlikely overflow bug in bms_next_member()
David Rowley <drowley@postgresql.org>
23:39 e3e26d04bd52 Fix unlikely overflow bug in bms_next_member()
David Rowley <drowley@postgresql.org>
23:39 e3e26d04bd52 Fix unlikely overflow bug in bms_next_member()
David Rowley <drowley@postgresql.org>
23:39 e3e26d04bd52 Fix unlikely overflow bug in bms_next_member()
David Rowley <drowley@postgresql.org>
23:39 e3e26d04bd52 Fix unlikely overflow bug in bms_next_member()
David Rowley <drowley@postgresql.org>
23:39 e3e26d04bd52 Fix unlikely overflow bug in bms_next_member()
David Rowley <drowley@postgresql.org>
23:39 e3e26d04bd52 Fix unlikely overflow bug in bms_next_member()
David Rowley <drowley@postgresql.org>
23:39 e3e26d04bd52 Fix unlikely overflow bug in bms_next_member()
David Rowley <drowley@postgresql.org>
23:39 e3e26d04bd52 Fix unlikely overflow bug in bms_next_member()
David Rowley <drowley@postgresql.org>
23:39 e3e26d04bd52 Fix unlikely overflow bug in bms_next_member()
David Rowley <drowley@postgresql.org>
23:39 e3e26d04bd52 Fix unlikely overflow bug in bms_next_member()
David Rowley <drowley@postgresql.org>
23:39 e3e26d04bd52 Fix unlikely overflow bug in bms_next_member()
David Rowley <drowley@postgresql.org>
23:39 e3e26d04bd52 Fix unlikely overflow bug in bms_next_member()
David Rowley <drowley@postgresql.org>
23:39 e3e26d04bd52 Fix unlikely overflow bug in bms_next_member()
David Rowley <drowley@postgresql.org>
23:39 e3e26d04bd52 Fix unlikely overflow bug in bms_next_member()
David Rowley <drowley@postgresql.org>
23:39 e3e26d04bd52 Fix unlikely overflow bug in bms_next_member()
David Rowley <drowley@postgresql.org>
23:39 e3e26d04bd52 Fix unlikely overflow bug in bms_next_member()
David Rowley <drowley@postgresql.org>
22:43 a63bbc811d41 Use stack-allocated StringInfoDatas, where possible
David Rowley <drowley@postgresql.org>
22:43 a63bbc811d41 Use stack-allocated StringInfoDatas, where possible
David Rowley <drowley@postgresql.org>
22:43 a63bbc811d41 Use stack-allocated StringInfoDatas, where possible
David Rowley <drowley@postgresql.org>
22:43 a63bbc811d41 Use stack-allocated StringInfoDatas, where possible
David Rowley <drowley@postgresql.org>
22:43 a63bbc811d41 Use stack-allocated StringInfoDatas, where possible
David Rowley <drowley@postgresql.org>
22:43 a63bbc811d41 Use stack-allocated StringInfoDatas, where possible
David Rowley <drowley@postgresql.org>
22:43 a63bbc811d41 Use stack-allocated StringInfoDatas, where possible
David Rowley <drowley@postgresql.org>
22:43 a63bbc811d41 Use stack-allocated StringInfoDatas, where possible
David Rowley <drowley@postgresql.org>
22:43 a63bbc811d41 Use stack-allocated StringInfoDatas, where possible
David Rowley <drowley@postgresql.org>
22:43 a63bbc811d41 Use stack-allocated StringInfoDatas, where possible
David Rowley <drowley@postgresql.org>
22:43 a63bbc811d41 Use stack-allocated StringInfoDatas, where possible
David Rowley <drowley@postgresql.org>
22:43 a63bbc811d41 Use stack-allocated StringInfoDatas, where possible
David Rowley <drowley@postgresql.org>
22:43 a63bbc811d41 Use stack-allocated StringInfoDatas, where possible
David Rowley <drowley@postgresql.org>
22:43 a63bbc811d41 Use stack-allocated StringInfoDatas, where possible
David Rowley <drowley@postgresql.org>
22:43 a63bbc811d41 Use stack-allocated StringInfoDatas, where possible
David Rowley <drowley@postgresql.org>
22:43 a63bbc811d41 Use stack-allocated StringInfoDatas, where possible
David Rowley <drowley@postgresql.org>
22:43 a63bbc811d41 Use stack-allocated StringInfoDatas, where possible
David Rowley <drowley@postgresql.org>
22:43 a63bbc811d41 Use stack-allocated StringInfoDatas, where possible
David Rowley <drowley@postgresql.org>
22:43 a63bbc811d41 Use stack-allocated StringInfoDatas, where possible
David Rowley <drowley@postgresql.org>
22:43 a63bbc811d41 Use stack-allocated StringInfoDatas, where possible
David Rowley <drowley@postgresql.org>
22:43 a63bbc811d41 Use stack-allocated StringInfoDatas, where possible
David Rowley <drowley@postgresql.org>
22:43 a63bbc811d41 Use stack-allocated StringInfoDatas, where possible
David Rowley <drowley@postgresql.org>
22:43 a63bbc811d41 Use stack-allocated StringInfoDatas, where possible
David Rowley <drowley@postgresql.org>
22:43 a63bbc811d41 Use stack-allocated StringInfoDatas, where possible
David Rowley <drowley@postgresql.org>
22:43 a63bbc811d41 Use stack-allocated StringInfoDatas, where possible
David Rowley <drowley@postgresql.org>
22:43 a63bbc811d41 Use stack-allocated StringInfoDatas, where possible
David Rowley <drowley@postgresql.org>
22:43 a63bbc811d41 Use stack-allocated StringInfoDatas, where possible
David Rowley <drowley@postgresql.org>
10:49 a78cf591a3f5 Doc: use "an SQL" consistently rather than "a SQL"
David Rowley <drowley@postgresql.org>
10:49 a78cf591a3f5 Doc: use "an SQL" consistently rather than "a SQL"
David Rowley <drowley@postgresql.org>
10:49 a78cf591a3f5 Doc: use "an SQL" consistently rather than "a SQL"
David Rowley <drowley@postgresql.org>
10:49 a78cf591a3f5 Doc: use "an SQL" consistently rather than "a SQL"
David Rowley <drowley@postgresql.org>
10:49 a78cf591a3f5 Doc: use "an SQL" consistently rather than "a SQL"
David Rowley <drowley@postgresql.org>
10:49 a78cf591a3f5 Doc: use "an SQL" consistently rather than "a SQL"
David Rowley <drowley@postgresql.org>
10:49 a78cf591a3f5 Doc: use "an SQL" consistently rather than "a SQL"
David Rowley <drowley@postgresql.org>
10:49 a78cf591a3f5 Doc: use "an SQL" consistently rather than "a SQL"
David Rowley <drowley@postgresql.org>
10:49 a78cf591a3f5 Doc: use "an SQL" consistently rather than "a SQL"
David Rowley <drowley@postgresql.org>
10:49 a78cf591a3f5 Doc: use "an SQL" consistently rather than "a SQL"
David Rowley <drowley@postgresql.org>
10:49 a78cf591a3f5 Doc: use "an SQL" consistently rather than "a SQL"
David Rowley <drowley@postgresql.org>
10:49 a78cf591a3f5 Doc: use "an SQL" consistently rather than "a SQL"
David Rowley <drowley@postgresql.org>
10:49 a78cf591a3f5 Doc: use "an SQL" consistently rather than "a SQL"
David Rowley <drowley@postgresql.org>
10:49 a78cf591a3f5 Doc: use "an SQL" consistently rather than "a SQL"
David Rowley <drowley@postgresql.org>
10:49 a78cf591a3f5 Doc: use "an SQL" consistently rather than "a SQL"
David Rowley <drowley@postgresql.org>
10:49 a78cf591a3f5 Doc: use "an SQL" consistently rather than "a SQL"
David Rowley <drowley@postgresql.org>
10:49 a78cf591a3f5 Doc: use "an SQL" consistently rather than "a SQL"
David Rowley <drowley@postgresql.org>
10:49 a78cf591a3f5 Doc: use "an SQL" consistently rather than "a SQL"
David Rowley <drowley@postgresql.org>
10:49 a78cf591a3f5 Doc: use "an SQL" consistently rather than "a SQL"
David Rowley <drowley@postgresql.org>
10:49 a78cf591a3f5 Doc: use "an SQL" consistently rather than "a SQL"
David Rowley <drowley@postgresql.org>
10:49 a78cf591a3f5 Doc: use "an SQL" consistently rather than "a SQL"
David Rowley <drowley@postgresql.org>
10:49 a78cf591a3f5 Doc: use "an SQL" consistently rather than "a SQL"
David Rowley <drowley@postgresql.org>
10:49 a78cf591a3f5 Doc: use "an SQL" consistently rather than "a SQL"
David Rowley <drowley@postgresql.org>
10:49 a78cf591a3f5 Doc: use "an SQL" consistently rather than "a SQL"
David Rowley <drowley@postgresql.org>
10:49 a78cf591a3f5 Doc: use "an SQL" consistently rather than "a SQL"
David Rowley <drowley@postgresql.org>
10:49 a78cf591a3f5 Doc: use "an SQL" consistently rather than "a SQL"
David Rowley <drowley@postgresql.org>
10:49 a78cf591a3f5 Doc: use "an SQL" consistently rather than "a SQL"
David Rowley <drowley@postgresql.org>