Re: copy-past-o comment in lock.h - Mailing list pgsql-hackers

From John Naylor
Subject Re: copy-past-o comment in lock.h
Date
Msg-id CACPNZCvOUFf6WZAw0BMzXyW7ToZhuFf12i+dd29Yb_nAtitmEA@mail.gmail.com
Whole thread Raw
In response to Re: copy-past-o comment in lock.h  (Michael Paquier <michael@paquier.xyz>)
Responses Re: copy-past-o comment in lock.h  (Michael Paquier <michael@paquier.xyz>)
List pgsql-hackers
On Wed, May 8, 2019 at 3:10 PM Michael Paquier <michael@paquier.xyz> wrote:
>
> On Tue, May 07, 2019 at 04:12:31PM +0800, John Naylor wrote:
> > That's probably better.
>
> Would you like to send an updated patch?  Perhaps you have a better
> idea?
> --
> Michael

In the attached, I've used your language, and also moved the comments
closer to the code they are describing. That seems more logical and
future proof.

-- 
John Naylor                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

Attachment

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Inconsistent error message wording for REINDEX CONCURRENTLY
Next
From: Michael Paquier
Date:
Subject: Re: copy-past-o comment in lock.h