From: | Thom Brown <thombrown(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | PGSQL Mailing List <pgsql-general(at)postgresql(dot)org>, rod(at)iol(dot)ie, Bruce Momjian <bruce(at)momjian(dot)us> |
Subject: | Re: Rename a constraint |
Date: | 2011-05-29 15:24:32 |
Message-ID: | BANLkTikqhWCaWBa=wppph=F0LXG_wCe26g@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 29 May 2011 16:12, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Thom Brown <thombrown(at)gmail(dot)com> writes:
>> On 10 January 2009 19:22, Raymond O'Donnell <rod(at)iol(dot)ie> wrote:
>>> On 10/01/2009 19:15, Thom Brown wrote:
>>>> I can't find anything in the documentation, but does anyone know if
>>>> there is a way to rename a constraint?
>
>>> I just tried it with a primary key...
>>>
>>> test=# alter table t1 alter constraint t1_pk rename to t1_pp;
>>> ERROR: syntax error at or near "constraint"
>>> LINE 1: alter constraint t1_pk rename to t1_pp;
>>>
>>> ... and as you can see it didn't work. I suppose you could always drop
>>> and recreate it with a different name.
>
>> While this was a sufficient solution for the problem I was having back
>> then, it will be problematic for those with large tables as it means
>> re-validating the constraint against the entire table.
>
> Use ALTER INDEX RENAME to rename the index underlying the constraint.
> The constraint will follow along.
Not all constraints are based on indexes though.
Thom
From | Date | Subject | |
---|---|---|---|
Next Message | Stefan Keller | 2011-05-29 17:45:15 | Re: How to check a table content efficiently? With LIMIT and OFFSET? |
Previous Message | Tom Lane | 2011-05-29 15:12:44 | Re: Rename a constraint |