Re: Typos in the code and README

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: David Rowley <dgrowleyml(at)gmail(dot)com>
Cc: Daniel Gustafsson <daniel(at)yesql(dot)se>, Alexander Lakhin <exclusion(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, Nazir Bilal Yavuz <byavuz81(at)gmail(dot)com>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Typos in the code and README
Date: 2024-09-05 00:03:26
Message-ID: Ztj1TqXMXGOyt-E4@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Sep 05, 2024 at 03:34:31AM +1200, David Rowley wrote:
> Anyway, I doubt hard
> guidelines are warranted here, but maybe some hints about best
> practices in https://wiki.postgresql.org/wiki/Committing_checklist ?

Yep, that may be useful. I just tend to be cautious because it can be
very easy to mess up things depending on the code path you're
manipulating, speaking with some.. Experience on the matter. And an
RC1 is kind of something to be cautious with.
--
Michael

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tender Wang 2024-09-05 01:40:18 Re: Eager aggregation, take 3
Previous Message Michael Paquier 2024-09-04 23:58:29 Re: Avoid overflowed array index (src/backend/utils/activity/pgstat.c)