Re: pg_dump --split patch

Поиск
Список
Период
Сортировка
От Andrew Dunstan
Тема Re: pg_dump --split patch
Дата
Msg-id 4D1A5D4E.8040103@dunslane.net
обсуждение исходный текст
Ответ на Re: pg_dump --split patch  (Joel Jacobson <joel@gluefinance.com>)
Ответы Re: pg_dump --split patch  (Joel Jacobson <joel@gluefinance.com>)
Re: pg_dump --split patch  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: pg_dump --split patch  (Gurjeet Singh <singh.gurjeet@gmail.com>)
Список pgsql-hackers

On 12/28/2010 04:44 PM, Joel Jacobson wrote:
>
>
>
>
>> The problem I see with suffixing a sequence id to the objects with 
>> name collision is that one day the dump may name myfunc(int) as 
>> myfunc.sql and after an overloaded version is created, say 
>> myfunc(char, int), then the same myfunc(int) may be dumped in 
>> myfunc-2.sql, which again is non-deterministic.
>
> I agree, good point!
> Perhaps abbreviations are to prefer, e.g., myfunc_i, myfunc_i_c, etc 
> to reduce the need of truncating filenames.
>
>
>

I think that's just horrible. Does the i stand for integer or inet? And 
it will get *really* ugly for type names with spaces in them ...


cheers

andrew


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

Предыдущее
От: Karl Lehenbauer
Дата:
Сообщение: Re: Patch to add table function support to PL/Tcl (Todo item)
Следующее
От: "Kevin Grittner"
Дата:
Сообщение: SSI SLRU strategy choices