-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Tom Lane wrote: |>Indicating that they should produce the same results, but that they work |>differently. I am not sure what that implies, but maybe someone else knows ? | The only difference the docs are talking about is what kind of lock is | held while the rebuild proceeds.
Yes I understood that, but the docs didn't (as you do now) excplicitly explain the different ways they work. I expected it to be as you say, however I was not 100% sure. Thanks for clarifying.
| A reindex builds a new index file from scratch, and AFAICS should give | the same results as dropping/recreating the index --- at least in terms | of what's in the file proper. The only theory I can come up with for | your experience is that there was some corruption in the system catalog | rows describing the index. That would not get fixed by a reindex. | However, I haven't the foggiest idea what sort of corruption might | allow the index to seem to work (and not, say, crash the reindex itself | which is going to use that information...) yet allow problems to appear | much later on. Too bad the evidence is gone now.
Yes, sorry about not bringing up the issue at the right time, however my main focus at that time was to bring the production system back to normal..
Regards - -- Denis -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2-nr2 (Windows XP)
iD8DBQFAnh+gvsCA6eRGOOARAlivAKCl8aIuii8GeSFLetWn+exBVXnptwCeKMUr wjAEgS7gP1LQeS/xZdiC03g= =ZRI6 -----END PGP SIGNATURE-----
---------------------------(end of broadcast)--------------------------- TIP 6: Have you searched our list archives?
http://archives.postgresql.org
