From: | Terry Lee Tucker <terry(at)esc1(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: pg_index question |
Date: | 2005-03-25 21:59:34 |
Message-ID: | 200503251659.34928.terry@esc1.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Well, I think I had the right oid, but I agree with you. I think I have a
better solution than this. I think I real try it once more though. I must
have done something wrong.
Thanks for the reply :o)
On Friday 25 March 2005 04:53 pm, Scott Marlowe saith:
> Umm, I tried it and it worked. Sure you got the right relid?
>
> On Fri, 2005-03-25 at 15:30, Terry Lee Tucker wrote:
> > To answer my own question, "No it won't work." I still get a unique
> > constraint error.
> >
> > On Friday 25 March 2005 04:10 pm, Terry Lee Tucker saith:
> > > Hi,
> > >
> > > If I were to set the value of pg_class.indisunique on a unique index to
> > > False inside a transaction so I could juggle sequence numbers around on
> > > a table with a unique two element index, and then set it back again to
> > > its proper value, all in the same transaction, would that allow me to
> > > temorarily override the unique index behavior? Is it safe to
> > > temporarily change the value of that column?
> > >
> > > ---------------------------(end of
> > > broadcast)--------------------------- TIP 2: you can get off all lists
> > > at once with the unregister command (send "unregister
> > > YourEmailAddressHere" to majordomo(at)postgresql(dot)org)
From | Date | Subject | |
---|---|---|---|
Next Message | OpenMacNews | 2005-03-25 23:16:12 | help w/ a little naive brainstorming ... |
Previous Message | Scott Marlowe | 2005-03-25 21:53:07 | Re: pg_index question |