From: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
---|---|
To: | Greg Stark <stark(at)mit(dot)edu> |
Cc: | pgsql-hackers(at)postgresql(dot)org, webmaster(at)postgresql(dot)org |
Subject: | Re: PostgreSQL commitfest: 2022-09-01 |
Date: | 2022-04-09 02:15:03 |
Message-ID: | 20220409021503.GO24419@telsasoft.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Apr 08, 2022 at 12:55:04PM +0000, webmaster(at)postgresql(dot)org wrote:
> The following patches that you follow, directly or indirectly,
> have received updates in the PostgreSQL commitfest app:
>
>
> Function to log backtrace of postgres processes
> https://commitfest.postgresql.org/38/2863/
>
> * New status: Needs review (stark)
> * Closed in commitfest 2022-03 with status: Moved to next CF (stark)
>
>
>
> Add --schema and --exclude-schema options to vacuumdb
> https://commitfest.postgresql.org/39/3587/
>
> * New status: Needs review (stark)
> * Closed in commitfest 2022-07 with status: Moved to next CF (stark)
The 2nd patch was already in July's CF, and it looks like you accidentally
moved it to July+1. AFAIK this requires a DBA to fix.
From | Date | Subject | |
---|---|---|---|
Next Message | Justin Pryzby | 2022-04-09 02:18:53 | cfbot requests |
Previous Message | Shinoda, Noriyoshi (PN Japan FSIP) | 2022-04-09 01:51:21 | RE: Expose JIT counters/timing in pg_stat_statements |