Re: pgsql-server: Clean up generation of default names

From: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>
To: Tom Lane <tgl(at)svr1(dot)postgresql(dot)org>
Cc: pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql-server: Clean up generation of default names
Date: 2004-06-11 01:14:37
Message-ID: 40C9077D.6050805@familyhealth.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

> Clean up generation of default names for constraints, indexes, and serial
> sequences, as per recent discussion. All these names are now of the
> form table_column_type, with digits added if needed to make them unique.
> Default constraint names are chosen to be unique across their whole schema,
> not just within the parent object, so as to be more SQL-spec-compatible
> and make the information schema views more useful.

Do you do any sort of 'locking of potential names' to ensure that
another process adding a sequence at the same time or something won't
get the same name first, causing yours to still fail or break uniqueness?

Or do we just not care since it's unlikely to happen and our transation
would likely have some exclusive lock anyway?

Chris

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2004-06-11 01:27:39 Re: pgsql-server: Fix oversight in recent ALTER TABLE
Previous Message Christopher Kings-Lynne 2004-06-11 01:13:15 Re: pgsql-server: Fix oversight in recent ALTER TABLE

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2004-06-11 01:19:39 Re: Delaying the planning of unnamed statements until Bind
Previous Message Alvaro Herrera 2004-06-11 00:54:02 Re: Nested xacts: looking for testers and review