| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Vincent Veyron <vv(dot)lists(at)wanadoo(dot)fr> |
| Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: unexpected character used as group separator by to_char |
| Date: | 2021-03-09 23:57:05 |
| Message-ID: | 2051063.1615334225@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Vincent Veyron <vv(dot)lists(at)wanadoo(dot)fr> writes:
> Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> (I suppose you could also use regexp_replace to convert random forms
>> of whitespace to plain ASCII space.)
> No dice. 'G' formatting looks like a whitespace, but is different (it appears to be slightly narrower when displayed in html, too) :
Huh ... do you have lc_monetary and lc_ctype set the same? The
latter is (I believe) what determines the behavior of regex \s.
In any case, you could force the issue with a pattern like '[\s\uNNNN]'
for whatever the code point of that character is.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2021-03-10 00:18:21 | Re: Need help with clarification on stored procedure support in PostGreSQL database |
| Previous Message | David G. Johnston | 2021-03-09 23:54:10 | Re: Need help with clarification on stored procedure support in PostGreSQL database |