From: | Anastasia Lubennikova <a(dot)lubennikova(at)postgrespro(dot)ru> |
---|---|
To: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Ready For Committer patches (CF 2020-11) |
Date: | 2020-11-24 20:18:44 |
Message-ID: | bfd24656-7ec5-03d3-78d2-199fa4f5d63b@postgrespro.ru |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
with this message, I want to draw attention to the RFC patches on the
current commitfest. It would be good if committers could take a look at
them.
While doing a sweep through the CF, I have kicked a couple of entries
back to Waiting on author, so now the list is correct. Now we have 17
entries.
https://commitfest.postgresql.org/30/?status=3
The oldest RFC patches are listed below. These entries are quite large
and complex. Still they got a good amount of reviews and it looks like
after a long discussion they are in a good shape.
Generic type subscripting <https://commitfest.postgresql.org/30/1062/>
schema variables, LET command <https://commitfest.postgresql.org/30/1608/>
pgbench - add pseudo-random permutation function
<https://commitfest.postgresql.org/30/2138/>
Allow REINDEX, CLUSTER and VACUUM FULL to rebuild on new
TABLESPACE/INDEX_TABLESPACE <https://commitfest.postgresql.org/30/2269/>
range_agg / multiranges <https://commitfest.postgresql.org/30/2112/>
--
Anastasia Lubennikova
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
From | Date | Subject | |
---|---|---|---|
Next Message | David Rowley | 2020-11-24 20:43:47 | Re: Keep elog(ERROR) and ereport(ERROR) calls in the cold path |
Previous Message | Tom Lane | 2020-11-24 19:48:06 | Re: mark/restore failures on unsorted merge joins |