Re: Assorted small doc patches

From: Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>
To: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Assorted small doc patches
Date: 2022-06-01 14:05:39
Message-ID: 0673ce25-1033-a89f-d4a4-80ea3fffc846@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 31.05.22 22:12, David G. Johnston wrote:
> Anything I should be doing differently here to get a bit of
> reviewer/committer time on these?  I'll add them to the commitfest for
> next month if needed but I'm seeing quick patches going in every week
> and the batch format done at the beginning of the month got processed
> through without issue.

These patches appear to have merit, but they address various nontrivial
areas of functionality, so either a) I just pick out a few that I
understand and deal with those and leave the rest open, or b) I'm
overwhelmed and do none. It might have been better to post these
separately.

I'll start with one though: v0001-database-default-name.patch

I don't understand why you propose this change. It appears to reduce
precision.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2022-06-01 14:11:16 Re: pg_upgrade test writes to source directory
Previous Message Bruce Momjian 2022-06-01 14:03:18 Re: Multi-Master Logical Replication