On Fri, Jul 22, 2022 at 03:33:20PM -0700, Peter Geoghegan wrote:
> On Fri, Jul 22, 2022 at 2:11 PM Bruce Momjian wrote:
> > I have improved the wording of the last paragraph in this patch.
>
> I think that it would be worth prominently explaining where heap-only
> tuples get their name from: it
On Sat, Jul 23, 2022 at 11:34 AM Peter Geoghegan wrote:
> On Sat, Jul 23, 2022 at 8:51 AM Bruce Momjian wrote:
> > Good points. I have updated the attached patch and URL to mention that
> > HOT rows are _completely_ removed, and why that is possible, and I
> > clarified the page item
On Sat, Jan 15, 2022 at 11:01:58PM +, PG Doc comments form wrote:
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/14/sql-createindex.html
> Description:
>
> In the CREATE INDEX
>
On Sat, Jul 23, 2022 at 8:51 AM Bruce Momjian wrote:
> Good points. I have updated the attached patch and URL to mention that
> HOT rows are _completely_ removed, and why that is possible, and I
> clarified the page item identifier mention.
I think that this version looks very good, but I do
> On 22 Jul 2022, at 16:32, Bruce Momjian wrote:
>
> On Wed, Jan 19, 2022 at 10:24:57AM +0100, Daniel Gustafsson wrote:
>>> On 17 Jan 2022, at 23:55, PG Doc comments form
>>> wrote:
>>
>>> The instructions say that I have to edit config.pl (actually, I had to
>>> create it)..
>>
>> I know
pg document is not recorded：maintenance_work_mem can not large than 2GB in
windows。
https://www.postgresql.org/docs/14/runtime-config-resource.html
I suggest that：modify maintenance_work_mem parameter description in the pg
documents：
add maintenance_work_mem parameter size limit in
