So, does it mean that the only way to disable the index is to drop and recreate it? What about setting indisunique to false temporarily?
-----Original Message----- From: Bruce Momjian [mailto:[EMAIL PROTECTED] Sent: Friday, January 09, 2004 10:19 AM To: Oleg Lebedev Cc: [EMAIL PROTECTED] Subject: Re: [GENERAL] deferring/disabling unique index Oleg Lebedev wrote: > Hi, > > I need to know if there is a way to defer or disable a unique index on > a table during an update. One way would be to set indisunique to > false, perform update and then set to true. But, this seems to be an > ugly solution. > > I've posted a similar message 6 months ago and at that time deferring > unique constraints was on a todo list. I wonder if this has been added > to 7.4.1 release. If not, what is the best way to disable an index on > a table? It is still not done, and no one is working on it. -- Bruce Momjian | http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073 ************************************* This e-mail may contain privileged or confidential material intended for the named recipient only. If you are not the named recipient, delete this message and all attachments. Unauthorized reviewing, copying, printing, disclosing, or otherwise using information in this e-mail is prohibited. We reserve the right to monitor e-mail sent through our network. ************************************* ---------------------------(end of broadcast)--------------------------- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
