| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
| Cc: | Torsten Förtsch <tfoertsch123(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Allowing pg_recvlogical to create temporary replication slots |
| Date: | 2024-10-31 00:12:07 |
| Message-ID: | ZyLLV3o8WTCcsnlh@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Oct 30, 2024 at 09:00:59AM +0100, Peter Eisentraut wrote:
> I think you should explain a bit why you want to do that, what use case or
> scenario this is meant to address.
Indeed. Note also this page giving a couple more guidelines with more
details:
https://wiki.postgresql.org/wiki/Submitting_a_Patch
We also use what we call a "commit fest" to keep a track of the
patches under review for the current development cycle. It is a
process where folks can register for patch reviews and provide
feedback. There is still time to register what you have here for the
commit fest beginning on the 1st of November:
https://commitfest.postgresql.org/50/
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2024-10-31 00:13:40 | Re: Having problems generating a code coverage report |
| Previous Message | Michael Paquier | 2024-10-30 23:47:04 | Re: Add isolation test template in injection_points for wait/wakeup/detach |