Re: move collation import to backend

Поиск
Список
Период
Сортировка
От Andres Freund
Тема Re: move collation import to backend
Дата
Msg-id 20161129195335.veosnf5rbrdmh346@alap3.anarazel.de
обсуждение исходный текст
Ответ на Re: move collation import to backend  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Ответы Re: move collation import to backend
Re: move collation import to backend
Список pgsql-hackers
On 2016-11-29 12:16:37 -0500, Peter Eisentraut wrote:
> On 11/12/16 10:38 AM, Andres Freund wrote:
> >>      /*
> >>      * Also forbid matching an any-encoding entry.  This test of course is not
> >>      * backed up by the unique index, but it's not a problem since we don't
> >>      * support adding any-encoding entries after initdb.
> >>      */
> > 
> > Note that this isn't true anymore...
> 
> I think this is still correct, because the collation import does not
> produce any any-encoding entries (collencoding = -1).

Well, the comment "don't support adding any-encoding entries after
initdb." is now wrong.

> >> +
> >> +Datum pg_import_system_collations(PG_FUNCTION_ARGS);
> >> +
> >> +Datum
> >> +pg_import_system_collations(PG_FUNCTION_ARGS)
> >> +{
> > 
> > Uh?
> 
> Required to avoid compiler warning about missing prototype.

It seems not to be project style to have prototypes in the middle of the
file...

- Andres



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

Предыдущее
От: Christian Ullrich
Дата:
Сообщение: Re: pgsql: Add putenv support for msvcrt from Visual Studio 2013
Следующее
От: Fabien COELHO
Дата:
Сообщение: Re: PSQL commands: \quit_if, \quit_unless