>
>
> > Anyway, I pushed the patch. I appreciate your willingness to
> > collaborate and look forward to your future participation, for sure.
Thank you Laurenz and Alvaro.
Regards,
Rajie
On Fri, May 20, 2022 at 3:55 PM Laurenz Albe
wrote:
> On Fri, 2022-05-20 at 10:30 +0200, Alvaro Herrera
On Fri, 2022-05-20 at 10:30 +0200, Alvaro Herrera wrote:
>
> Anyway, I pushed the patch. I appreciate your willingness to
> collaborate and look forward to your future participation, for sure.
Thanks!
Laurenz Albe
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
On Fri, 2022-05-20 at 10:14 +0530, Rajakavitha Kodhandapani wrote:
> 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 sense.
> > > I will make the updates and
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
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
Thank you, Laurenz. The changes that you suggested make a lot more sense.
I will make the updates and submit the changes.
Regards,
Rajie
On Thu, May 19, 2022 at 9:45 PM Lauren Fliksteen
wrote:
> Thank you both! I think Laurenz’s changes make perfect sense!
>
> Sent from my iPhone
>
> > On May
Thank you both! I think Laurenz’s changes make perfect sense!
Sent from my iPhone
> On May 19, 2022, at 8:37 AM, Laurenz Albe wrote:
>
> On Thu, 2022-05-19 at 19:02 +0530, Rajakavitha Kodhandapani wrote:
>>> I think the INVALID index can use further explanation, in particular, from
>>> my
On Thu, 2022-05-19 at 19:02 +0530, Rajakavitha Kodhandapani wrote:
> > I think the INVALID index can use further explanation, in particular, from
> > my experience it seems like when building an index concurrently, the index
> > gets inserted and labeled invalid while the index is being built, and
Hi,
This is my first attempt at contributing to the documentation of PostgreSQL.
Here's the patch. Please let me know if any other changes need to be made.
Regards,
Rajie
On Thu, May 19, 2022 at 1:10 AM PG Doc comments form
wrote:
> The following documentation comment has been logged on the
10 matches
Mail list logo
