| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Murtuza Zabuawala <murtuza(dot)zabuawala(at)enterprisedb(dot)com> |
| Cc: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, PostgreSQL mailing lists <pgsql-general(at)postgresql(dot)org>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [GENERAL] Not able to create collation on Windows |
| Date: | 2017-08-01 16:58:50 |
| Message-ID: | 6289.1501606730@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
Murtuza Zabuawala <murtuza(dot)zabuawala(at)enterprisedb(dot)com> writes:
> Yes, I was able to create collation using "C" instead of "POSIX" on windows,
> CREATE COLLATION public.test from pg_catalog."C";
Yeah, I thought that might happen. So the point basically is that in
almost all of the collations code, the "C" and "POSIX" names are handled
by dedicated code paths that don't care what the system's locale support
thinks. But we missed that for CREATE COLLATION. Aside from the case
you ran into, this means you can't do CREATE COLLATION ... FROM "C"
at all on platforms that lack HAVE_LOCALE_T. There's no good reason
for that IMO; not if we're one line of code away from allowing it.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2017-08-01 18:32:27 | Re: standby database crash |
| Previous Message | Murtuza Zabuawala | 2017-08-01 16:33:02 | Re: [GENERAL] Not able to create collation on Windows |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2017-08-01 17:11:55 | Re: [PATCH v3] pg_progress() SQL function to monitor progression of long running SQL queries/utilities |
| Previous Message | Tom Lane | 2017-08-01 16:51:52 | Re: PL_stashcache, or, what's our minimum Perl version? |