public inbox for [email protected]  

help / color / mirror / Atom feed

From: Rajakavitha Kodhandapani <[email protected]>
To: Alvaro Herrera <[email protected]>
Cc: Lauren Fliksteen <[email protected]>
Cc: Laurenz Albe <[email protected]>
Cc: [email protected]
Subject: Re: INVALID index while concurrent indexing in progress?
Date: Fri, 20 May 2022 10:14:24 +0530
Message-ID: <CABx-2BDH8VSPjk-A5qoN0J8H4T_uPW7pB1xmT3dbUidK5_==Vw@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <CABx-2BAHnpxPBzig7ucjYebjFeUYsiogSvT8CuRDgCFVBdGSKg@mail.gmail.com>
	<[email protected]>

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 suffix
   manually. Using the ".patch" extension allows some reviewers to more easily
   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
   <https://www.postgresql.org/list/pgsql-hackers/;. Don't expect that
   everyone will still be able to find previous submissions on their own. You
   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 <[email protected]>
wrote:

> On 2022-May-19, Rajakavitha Kodhandapani wrote:
>
> > Thank you, Laurenz. The changes that you suggested make a lot more sense.
> > I will make the updates and submit the changes.
>
> Hmm, but they're already submitted.
>
> --
> Álvaro Herrera               48°01'N 7°57'E  —
> https://www.EnterpriseDB.com/
> "La victoria es para quien se atreve a estar solo"
>

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected], [email protected]
  Subject: Re: INVALID index while concurrent indexing in progress?
  In-Reply-To: <CABx-2BDH8VSPjk-A5qoN0J8H4T_uPW7pB1xmT3dbUidK5_==Vw@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox