From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
Cc: | "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Docs for pg_basebackup needs v17 note for incremental backup |
Date: | 2025-02-06 14:43:17 |
Message-ID: | CAKFQuwa3XH3NLTB9o7a+QByO3yTpxiieAg=w5r80MuZR_Dyp=A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thursday, February 6, 2025, Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
> On 2025-02-05 We 7:59 PM, David G. Johnston wrote
>
>
> People get busy. For example, many prominent hackers spent most of the
> last week at various conferences. There are also other things happening
> less publicly that are claiming people's time.
>
>
Those prominent hackers are getting the benefit of me being one of the more
prolific community question takers which lets them spend more time hacking.
While I’m not entitled to anything I suggest you all consider that a
failure to acknowledge my patch requests is frustrating enough for me that
I’m about to just give up and walk away, leaving you all to deal with those
user questions more frequently. The vast majority of emails get responses
in some form with a day or so and lots of patches have gone in outside the
commitfest process within days of initial reporting while I play by the
rules and am a large contributor to the community but presently have 7
patches languishing in limbo, most without a single comment for or against.
This is just one of the more clear-cut ones that doesn’t even take a senior
hacker to deal with and, frankly, whomever put in incremental backup should
have seen the title and dealt with it immediately, even if I didn’t copy
them, IMO.
David J.
From | Date | Subject | |
---|---|---|---|
Next Message | jian he | 2025-02-06 14:49:00 | Re: Re: proposal: schema variables |
Previous Message | vignesh C | 2025-02-06 13:56:33 | Re: Introduce XID age and inactive timeout based replication slot invalidation |