| From: | "Robin Haberkorn" <haberkorn(at)b1-systems(dot)de> |
|---|---|
| To: | "Pavel Luzanov" <p(dot)luzanov(at)postgrespro(dot)ru>, "Abhishek Chanda" <abhishek(dot)becs(at)gmail(dot)com> |
| Cc: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "PostgreSQL Hackers" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Adding error messages to a few slash commands |
| Date: | 2025-05-12 21:00:17 |
| Message-ID: | D9UHGDQD1455.3D1NL25XC82LO@b1-systems.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon Apr 14, 2025 at 12:27:53 GMT +03, Pavel Luzanov wrote:
> I recommend to create a new entry for this patch in the open July
> commitfest <https://commitfest.postgresql.org/53/>.
> I will be able to review this patch in a couple months later in June,
> if no one wants to review it earlier.
I could review it right now, i.e. do a pre-commit review according to [1].
Still have to "pay off" my own Commitfest entry. This would be my first PG
review. But is it even desirable to write reviews before the beginning of the
Commitfest? An important part -- especially in simple patches like this one
-- would be to apply it to HEAD. And shouldn't that be better done as late as
possible?
[1] https://wiki.postgresql.org/wiki/Reviewing_a_Patch
--
Robin Haberkorn
Senior Software Engineer
B1 Systems GmbH
Osterfeldstraße 7 / 85088 Vohburg / https://www.b1-systems.de
GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt, HRB 3537
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nico Williams | 2025-05-12 21:31:22 | Re: Proposal: Exploring LSM Tree‑Based Storage Engine for PostgreSQL (Inspired by MyRocks) |
| Previous Message | Aleksander Alekseev | 2025-05-12 20:58:49 | Re: Proposal: Exploring LSM Tree‑Based Storage Engine for PostgreSQL (Inspired by MyRocks) |