From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | James Robinson <jlrobins(at)socialserve(dot)com> |
Cc: | pgsql-docs(at)postgresql(dot)org |
Subject: | Re: create index concurrently docs ... |
Date: | 2007-02-04 01:27:43 |
Message-ID: | 200702040127.l141Rhk17779@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
Does anyone know the answer to this? I couldn't find it, but it is a
good quesiton.
---------------------------------------------------------------------------
James Robinson wrote:
> In reading over the caveats regarding create index concurrently, I
> think it'd be nice to see an example of what the return result will
> be if an 'invalid' index is created so a dba who read the docs night
> recognize the error, as well as for searchengine fodder to find out
> what to do real fast if such an error happens to them.
>
> Something around this paragraph in http://www.postgresql.org/docs/
> current/static/sql-createindex.html#SQL-CREATEINDEX-CONCURRENTLY:
>
> "If a problem arises during the second scan of the table, such as a
> uniqueness violation in a unique index, the CREATE INDEX command will
> fail but leave behind an "invalid" index."
>
> Thanks!
> ----
> James Robinson
> Socialserve.com
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/docs/faq
--
Bruce Momjian bruce(at)momjian(dot)us
EnterpriseDB http://www.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
From | Date | Subject | |
---|---|---|---|
Next Message | bubblboy | 2007-02-07 02:46:00 | Online documentation unclear about authentication defaults |
Previous Message | Andrew Sullivan | 2007-02-02 16:46:38 | Re: "May", "can", "might" |