Re: [PATCH] Comment typo in get_collation_name() comment

From: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
To: Dagfinn Ilmari Mannsåker <ilmari(at)ilmari(dot)org>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: [PATCH] Comment typo in get_collation_name() comment
Date: 2018-01-03 22:14:08
Message-ID: 20180103221408.fpyga7at4kqfk577@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

Dagfinn Ilmari Mannsåker wrote:
> ilmari(at)ilmari(dot)org (Dagfinn Ilmari Mannsåker) writes:
> > Hi Hackers,
> >
> > The comment for get_collation_name() seems to have been copy-pasted from
> > get_constraint_name(), but missed one s/constraint/collation/.
> >
> > Patch attached.
> Bump? Do I need to add this patch to the next commitfest? I thought
> trivial comment typo patches like this generally got commited without
> such bureaucracy?

The problem is that pg-hackers is now too much traffic, so unregistered
patches customarily fall through cracks. Recommendation is to register
all patches to avoid that problem.

I have pushed it now.

Álvaro Herrera
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Dagfinn Ilmari =?utf-8?Q?Manns=C3=A5ker?= 2018-01-03 22:17:22 Re: compress method for spgist - 2
Previous Message Alvaro Herrera 2018-01-03 22:11:00 Re: [Patch v2] Make block and file size for WAL and relations defined at cluster creation