Re: speed up unicode normalization quick check

From: John Naylor <john(dot)naylor(at)enterprisedb(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Masahiko Sawada <masahiko(dot)sawada(at)2ndquadrant(dot)com>, Mark Dilger <mark(dot)dilger(at)enterprisedb(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: speed up unicode normalization quick check
Date: 2020-10-20 09:33:43
Message-ID: CAFBsxsFXiBYAxgR4uMv4NjqN10eOP7mPdhPFc7b+gtgS_h=6jg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Oct 19, 2020 at 9:49 PM Michael Paquier <michael(at)paquier(dot)xyz> wrote:

>
> The aligned numbers have the advantage to make the checks of the code
> generated easier, for the contents and the format produced. So using
> a right padding as you are suggesting here rather than a new exception
> in .gitattributes sounds fine to me. I simplified things a bit as the
> attached, getting rid of the last comma while on it. Does that look
> fine to you?
>

This is cleaner, so I'm good with this.

--
John Naylor
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bharath Rupireddy 2020-10-20 09:55:14 Re: Parallel copy
Previous Message David Rowley 2020-10-20 09:30:55 Re: Hybrid Hash/Nested Loop joins and caching results from subplans