Changes to pg_dump/psql following collation "C" in the catalog

Поиск
Список
Период
Сортировка
От Daniel Verite
Тема Changes to pg_dump/psql following collation "C" in the catalog
Дата
Msg-id 701e51f0-0ec0-4e70-a365-1958d66dd8d2@manitou-mail.org
обсуждение исходный текст
Ответы Re: Changes to pg_dump/psql following collation "C" in the catalog  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers
 Hi,

One consequence of using the "C" collation in the catalog versus
the db collation is that pg_dump -t with a regexp may not find
the same tables as before. It happens when these conditions are
all met:
- the collation of the database is not "C"
- the regexp has locale-dependant parts
- the names to match include characters that are sensitive to
locale-dependant matching

For instance a table named "rapport_journée_12" in an fr_FR.UTF-8 db
used to be found by pg_dump -t 'rapport_\w+_\d+', and is now missed
in the devel version.

It seems that to fix that, we could qualify the references to columns such
as "relname" and "schema_name" with COLLATE "default" clauses in the
queries that use pattern-matching in client-side tools, AFAICS
pg_dump and psql.

Before going any further with this idea, is there agreement that it's an
issue to address and does this look like the best way to do that?


Best regards,
--
Daniel Vérité
PostgreSQL-powered mailer: http://www.manitou-mail.org
Twitter: @DanielVerite


В списке pgsql-hackers по дате отправления:

Предыдущее
От: ilmari@ilmari.org (Dagfinn Ilmari Mannsåker)
Дата:
Сообщение: Re: [PATCH] Improve tab completion for CREATE TABLE
Следующее
От: Alvaro Herrera
Дата:
Сообщение: Re: tickling the lesser contributor's withering ego