Skip site navigation (1) Skip section navigation (2)

Re: pgsql: Add function to import operating system collations

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql: Add function to import operating system collations
Date: 2017-01-18 14:53:16
Message-ID: 26116.1484751196@sss.pgh.pa.us (view raw, whole thread or download thread mbox)
Thread:
Lists: pgsql-committerspgsql-hackers
Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> Add function to import operating system collations

The buildfarm's not happy with this, and neither am I:

...
creating configuration files ... ok
running bootstrap script ... ok
performing post-bootstrap initialization ... 2017-01-18 09:49:45.019 EST [25919] FATAL:  collation "aa_ER(at)saaho" for encoding "UTF8" already exists
2017-01-18 09:49:45.019 EST [25919] STATEMENT:  SELECT pg_import_system_collations(if_not_exists => false, schema => 'pg_catalog');

child process exited with exit code 1
initdb: removing data directory "/home/postgres/testversion/data"

For reference, I get this on my RHEL6 installation:

$ locale -a | grep ^aa_ER
aa_ER
aa_ER.utf8
aa_ER(dot)utf8(at)saaho
aa_ER(at)saaho
$

Please fix ASAP, or revert so other people can get work done.

			regards, tom lane


In response to

Responses

pgsql-hackers by date

Next:From: Vladimir RusinovDate: 2017-01-18 15:09:32
Subject: Re: [PATCH] Rename pg_switch_xlog to pg_switch_wal
Previous:From: Alvaro HerreraDate: 2017-01-18 14:40:44
Subject: Re: References to arbitrary database objects that are suitable for pg_dump

pgsql-committers by date

Next:From: Tom LaneDate: 2017-01-18 15:43:07
Subject: Re: pgsql: Add function to import operating system collations
Previous:From: Peter EisentrautDate: 2017-01-18 14:36:08
Subject: pgsql: Add function to import operating system collations

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group