Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nruVG-0007xg-Hj for pgsql-docs@arkaria.postgresql.org; Fri, 20 May 2022 04:44:42 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nruVF-00052s-EQ for pgsql-docs@arkaria.postgresql.org; Fri, 20 May 2022 04:44:41 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nruVF-00052j-5P for pgsql-docs@lists.postgresql.org; Fri, 20 May 2022 04:44:41 +0000 Received: from mail-pj1-x102f.google.com ([2607:f8b0:4864:20::102f]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1nruVB-00010C-Qd for pgsql-docs@lists.postgresql.org; Fri, 20 May 2022 04:44:40 +0000 Received: by mail-pj1-x102f.google.com with SMTP id l14so7036507pjk.2 for ; Thu, 19 May 2022 21:44:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=xhUHusx4G0KXvNvclD6yH43IJWUBdnnOE0p1WWBiZrI=; b=PulECsJ37Ajzbq9fGmjPIMTAFGiIjqkEhx/sVxJfT0SAXcsdQ1NfMzogjCeqQl7CGX PIn+g+pFMfQIDGDZKCHV5pP14oqRy+81WIvutMtFS72p0dBvcpCaTB9WvC3M9PeAhZ9r 6oG6pUOupjdoK036BKsrDK9sOHzdmbKJcPSqqy+dqtNVilIEGU6agmoLUHfZ9ub3KzjM T0SUVYYj2yi03QDoUP///Aqf7h9Zf9Eoqd4E4EY3XcvdSmiJuR9zmfTW6MGy0KemUEly L+RifHzMLtn2B8zkEqrMS1DxKxbYjCcWCgn6GgBvzdIB/7jOLf06Q7et4y/SP48G5WjS xRkg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=xhUHusx4G0KXvNvclD6yH43IJWUBdnnOE0p1WWBiZrI=; b=3aNOYwiC5t8cFENhXHfEGr2g05dRs+NvVJNeeXCZnjuH4eyKycvjHF//OsGOO9SBel 8Fc+/zkLvLtbvy4nqjg3cg/JcnoXmGIJY7+J9icbA1q/xT29sLwgPWHJvGmU5RNNbYeV yu0RU/lILdbybzBY66NKQLKi2F6qhfoPl2GZeSH7Pm4MKWwxmYQVtWdFL2VuQVNR1Mcz a+A/NTuHK+xeW1W+AADRv8G1pW+cIGzoc93S2vQjiXguXs3RtOkiS5LasoM0cGyellJi cLSZZ8G0hTsoS555K8Dq0b4VvQaB23/b8vTZUdKZr4eFJYdAJx4tvs1aNDR3ki9KyiBI A8RA== X-Gm-Message-State: AOAM532z7EWKfG7PBYEN6yBIYtuXhikkVTU6T0awOds0eHp4/fh8LUjf r0F6GX7DWd2Tt36Sx2wY6VRmBo3gkHpXNZguDqI= X-Google-Smtp-Source: ABdhPJwhlqgpnW5Ad/C1X9BOfGIRMDe7MS2yOkfUUJUuVP96RHcJxRmDx55nt7a8GwZyiAmU8GKhZJpxxMxDirH4Ndw= X-Received: by 2002:a17:902:bc8c:b0:15e:c103:940c with SMTP id bb12-20020a170902bc8c00b0015ec103940cmr7892963plb.154.1653021875603; Thu, 19 May 2022 21:44:35 -0700 (PDT) MIME-Version: 1.0 References: <202205191636.q7kay3oesfwc@alvherre.pgsql> In-Reply-To: <202205191636.q7kay3oesfwc@alvherre.pgsql> From: Rajakavitha Kodhandapani Date: Fri, 20 May 2022 10:14:24 +0530 Message-ID: Subject: Re: INVALID index while concurrent indexing in progress? To: Alvaro Herrera Cc: Lauren Fliksteen , Laurenz Albe , pgsql-docs@lists.postgresql.org Content-Type: multipart/alternative; boundary="000000000000b38c7005df6a25e5" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000b38c7005df6a25e5 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Alvaro, I am new to PostgreSQL and still in the process of getting familiar with the workflow. Please let me know if I am missing something? My understanding was based on: https://wiki.postgresql.org/wiki/Submitting_a_Patch Submitting patch updates When submitting a new version of a previously submitted patch, you should do a few additional things: - Uniquely identify the new version. You can use git format-patch -vN, incrementing N each time; or you can add an incrementing numerical suffi= x manually. Using the ".patch" extension allows some reviewers to more eas= ily read it in their email client/code editor. - Make sure it's easy to find any earlier discussion of the patch, by providing Message-Id-based links to the mailing list posts . Don't expect that everyone will still be able to find previous submissions on their own. Y= ou can usually get the message ID of your email by looking for the header *Message-Id* in your email client. Try *View message source* or *View original* if it's not obviously visible. Regards, Rajie On Thu, May 19, 2022 at 10:06 PM Alvaro Herrera wrote: > On 2022-May-19, Rajakavitha Kodhandapani wrote: > > > Thank you, Laurenz. The changes that you suggested make a lot more sens= e. > > I will make the updates and submit the changes. > > Hmm, but they're already submitted. > > -- > =C3=81lvaro Herrera 48=C2=B001'N 7=C2=B057'E =E2=80=94 > https://www.EnterpriseDB.com/ > "La victoria es para quien se atreve a estar solo" > --000000000000b38c7005df6a25e5 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Alvaro,

I am new to PostgreSQL and s= till in the process of getting familiar=C2=A0with the workflow.
P= lease let me know if I am missing something?

Submitting patch updates

Wh= en submitting a new version of a previously submitted patch, you should do = a few additional things:

  • Uniquely identify the new vers= ion. You can use=C2=A0gi= t format-patch -vN, incrementing N each time; or you can add an incr= ementing numerical suffix manually. Using the ".patch" extension = allows some reviewers to more easily read it in their email client/code edi= tor.


On Thu, May 19, 2022 at 10:06 PM Alvaro Herrera <alvherre@alvh.no-ip.org> wrote:
On 2022-May-19, Rajakavitha Ko= dhandapani wrote:

> Thank you, Laurenz. The changes that you suggested make a lot more sen= se.
> I will make the updates and submit the changes.

Hmm, but they're already submitted.

--
=C3=81lvaro Herrera=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A04= 8=C2=B001'N 7=C2=B057'E=C2=A0 =E2=80=94=C2=A0 https://www.Enter= priseDB.com/
"La victoria es para quien se atreve a estar solo"
--000000000000b38c7005df6a25e5--