Re: [BUGS] Bug #581: Sequence cannot be deleted

Поиск
Список
Период
Сортировка
От Ian Barwick
Тема Re: [BUGS] Bug #581: Sequence cannot be deleted
Дата
Msg-id 200202122158.WAA00609@post.webmailer.de
обсуждение исходный текст
Ответ на Re: [BUGS] Bug #581: Sequence cannot be deleted  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: [BUGS] Bug #581: Sequence cannot be deleted  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: [BUGS] Bug #581: Sequence cannot be deleted  ("Tom Innes" <tinnes@inforamp.net>)
Список pgsql-hackers
On Tuesday 12 February 2002 21:48, Tom Lane wrote:
> I believe that the surprising-name problem will largely go away anyway
> as soon as we get around to increasing the default NAMEDATALEN.  With
> a decent name length no one would ever see truncation in practice.

Sorry to butt in here, but I would second this suggestion. One of my databases
has rather long-winded table and field names (mostly in German, which doesn't
help much ;-). There aren't any which exceed 31 characters on their own, but
sequences can get scarily long, so I always build with NAMEDATALEN set to 128,
just to be on the safe side.

Is there any reason for the default value (31 characters?), or are there
any performance issues associated with longer values?

> Also, of course, what we really want is for SERIAL sequences to get
> dropped by themselves when the parent table is dropped, and then users
> don't need to know what the generated sequence name is ...

This would be nice.

Yours

Ian Barwick


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

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: Maintaining the list of release changes
Следующее
От: Tom Lane
Дата:
Сообщение: Re: Add free-behind capability for large sequential scans