Re: [PATCH] Comment typo in get_collation_name() comment - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: [PATCH] Comment typo in get_collation_name() comment
Date
Msg-id 20180103221408.fpyga7at4kqfk577@alvherre.pgsql
Whole thread Raw
In response to Re: [PATCH] Comment typo in get_collation_name() comment  (ilmari@ilmari.org (Dagfinn Ilmari Mannsåker))
Responses Re: [PATCH] Comment typo in get_collation_name() comment
List pgsql-hackers
Dagfinn Ilmari Mannsåker wrote:
> ilmari@ilmari.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                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services


pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: [Patch v2] Make block and file size for WAL and relationsdefined at cluster creation
Next
From: ilmari@ilmari.org (Dagfinn Ilmari Mannsåker)
Date:
Subject: Re: compress method for spgist - 2