Re: postgres index rebuild

From: Jashobanta Mahapatra <jashobanta(dot)mahapatra(at)mahindracomviva(dot)com>
To: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Euler Taveira <euler(at)timbira(dot)com(dot)br>
Cc: "pgsql-docs(at)postgresql(dot)org" <pgsql-docs(at)postgresql(dot)org>
Subject: Re: postgres index rebuild
Date: 2017-05-29 04:58:26
Message-ID: EC7D716DA3C62341848CDCC6623FB859376CABED@COMV-MBX02-GGN.COMVIVA.COM
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs

Hi ,

Thank you so much for your quick response.

I have a doubt when you told script.
Are you talking about Shell scripting/ Perl Scripting or any other script.

It 'll be a great pleasure if you can help me with a small example.

-----Original Message-----
From: Michael Paquier [mailto:michael(dot)paquier(at)gmail(dot)com]
Sent: Saturday, May 27, 2017 1:44 AM
To: Euler Taveira
Cc: Jashobanta Mahapatra; pgsql-docs(at)postgresql(dot)org
Subject: Re: [DOCS] postgres index rebuild

On Fri, May 26, 2017 at 3:24 PM, Euler Taveira <euler(at)timbira(dot)com(dot)br> wrote:
> CIC can't be executed inside a transaction block or a user-defined
> function because it involves some phases that are not easily
> rollback-able. Instead create a small script with those commands.

If you are interested in the reasons why multiple transactions are needed, just go through DefineIndex() in indexcmds.c, particularly the comments. It explains all the phases that are happening for a concurrent index build, what are the validation phases, what are the wait phases, etc. The same applies for DROP INDEX with index_drop() in index.c.
--
Michael
This e-mail and all material transmitted with it are for the use of the intended recipient(s) ONLY and contains confidential and/or privileged information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies and the original message. Any unauthorized review, use, disclosure, dissemination, forwarding, printing or copying of this email or any action taken pursuant to the contents of the present e-mail is strictly prohibited and is unlawful. The recipient acknowledges that Comviva Technologies Limited or its management or directors, are unable to exercise control or ensure the integrity over /of the contents of the information contained in e-mail. Any views expressed herein are those of the individual sender only and no binding nature of the contents shall be implied or assumed unless the sender does so expressly with due authority of Comviva Technologies Limited. E-mail and any contents transmitted with it are prone to viruses and related defects despite all efforts to avoid such by Comviva Technologies Limited.

In response to

Browse pgsql-docs by date

  From Date Subject
Next Message Heikki Linnakangas 2017-05-29 06:32:21 Re: SCRAM RFC
Previous Message Michael Paquier 2017-05-28 03:13:45 Re: SCRAM RFC