Re: pgsql: Update high level vacuumlazy.c comments.

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Peter Geoghegan <pg(at)bowt(dot)ie>
Cc: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, pgsql-committers <pgsql-committers(at)lists(dot)postgresql(dot)org>
Subject: Re: pgsql: Update high level vacuumlazy.c comments.
Date: 2021-12-01 14:16:09
Message-ID: CA+TgmoYdp4qy2LFW7yCi6yFJ1m-RCH+npctJQd29k6d6uCx0ww@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

On Tue, Nov 30, 2021 at 3:45 PM Peter Geoghegan <pg(at)bowt(dot)ie> wrote:
> On Tue, Nov 30, 2021 at 12:20 PM Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> > +1. And that shouldn't happen often.
>
> Why shouldn't it happen often?
>
> I accept that I ought to have included a discussion link in this
> instance. But I don't see how that's related to how often I commit
> things where including a discussion link is unnecessary (per the
> general convention for these things).

Because there aren't many things that are so mechanical that there's
no reason to give people an opportunity to comment. Sure, if you're
just changing "teh" to "the" that's boring and there's nothing to talk
about. But if you're doing that every day, you should consolidate your
typo fix patches a bit so we don't clutter the commit history. If
you're making changes that people might disagree with, it's polite to
give them an opportunity to object before you commit. Even if most of
the time they don't.

--
Robert Haas
EDB: http://www.enterprisedb.com

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Peter Eisentraut 2021-12-01 14:22:32 pgsql: Warning on SET of nonexisting setting with a prefix reserved by
Previous Message Daniel Gustafsson 2021-12-01 14:01:44 pgsql: Fix certificate paths to use perl2host