From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
---|---|
To: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
Cc: | Rajakavitha Kodhandapani <krajakavitha(at)gmail(dot)com>, Lauren Fliksteen <dancernerd32(at)gmail(dot)com>, pgsql-docs(at)lists(dot)postgresql(dot)org |
Subject: | Re: INVALID index while concurrent indexing in progress? |
Date: | 2022-05-20 08:30:54 |
Message-ID: | 202205200830.dnekua6b2hhb@alvherre.pgsql |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
On 2022-May-20, Laurenz Albe wrote:
> Alvaro meant that my message already contained a patch, so there is no need to
> send another one, unless you have a different suggestion.
Right. Being old-school, I can just save the email to a plain text file
and do "patch < /tmp/emailfile". 'patch' has smarts to detect
irrelevant parts of the message, so the complete email works fine as a
patch.
> Added value could be a suggested commit message with "git
> format-patch" that could make the committer's job easier.
Right -- especially so if it comes with Author/Discussion/etc lines. (I
don't think I've seen any patch submitter do that.)
Anyway, I pushed the patch. I appreciate your willingness to
collaborate and look forward to your future participation, for sure.
--
Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/
"World domination is proceeding according to plan" (Andrew Morton)
From | Date | Subject | |
---|---|---|---|
Next Message | Laurenz Albe | 2022-05-20 10:25:23 | Re: INVALID index while concurrent indexing in progress? |
Previous Message | Laurenz Albe | 2022-05-20 06:59:30 | Re: INVALID index while concurrent indexing in progress? |