Thats the way my graphical DB dezign tool does it.
Tom Lane wrote:
> "Ivar" <ivar@lumisoft.ee> writes:
>
>>"Jan Wieck" <JanWieck@Yahoo.com> wrote
>>
>>>We maybe should relocate auto-created indexes for UNIQUE and PKEY
>>>definitions into some sort of special schema and give them funny names?
>
>
>>MS SQL adds funny names as columnName_236321_215251_156, seems that adds
>>some random at end to avoid similar errors.
>
>
> I think it's good that the index name is predictable. I think we should
> stick to the existing behavior as much as we can.
>
> It would probably make sense to check if the generated name is actually
> unused, and to stick some digits on the end if not. For example, try
> tab_col_key
> tab_col_key1
> tab_col_key2
> etc. until we find an unused name. Of course this is still subject to
> race conditions, but I think in practice it will solve the problem.
>
> regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/docs/faqs/FAQ.html
>