| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | "Karl O(dot) Pinc" <kop(at)meme(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Doc patch: Document names of automatically created constraints and indexes |
| Date: | 2012-11-24 23:02:41 |
| Message-ID: | 1353798161.4992.3.camel@vanquo.pezone.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, 2012-11-21 at 23:56 -0600, Karl O. Pinc wrote:
> No, wait. If constraint "name_of_primary_key" is an internal
> and is to change over time, how do you deal with dropping,
> now, a primary key constraint that was created, then, before
> some change to the internal name. And you wouldn't want
> to accidentally remove a user-created constraint
> that just happened to have the same name as the internal
> primary key constraint name, especially in the case
> where there's a real primary key constraint created
> under an old naming convention.
Internally, dependencies are tracked by OID, not by name, so this isn't
a problem.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit kapila | 2012-11-25 05:01:12 | Re: Proposal for Allow postgresql.conf values to be changed via SQL |
| Previous Message | Peter Eisentraut | 2012-11-24 23:01:32 | Re: Doc patch: Document names of automatically created constraints and indexes |