Re: Document atthasmissing default optimization avoids verification table scan - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Document atthasmissing default optimization avoids verification table scan
Date
Msg-id CA+TgmoaY0+udh52Q-71FjmpyrY9w37oW+dZ0f-_nr7aMcRt-gA@mail.gmail.com
Whole thread Raw
In response to Re: Document atthasmissing default optimization avoids verification table scan  (James Coleman <jtc331@gmail.com>)
Responses Re: Document atthasmissing default optimization avoids verification table scan  (James Coleman <jtc331@gmail.com>)
List pgsql-hackers
On Sun, Mar 27, 2022 at 1:00 PM James Coleman <jtc331@gmail.com> wrote:
> So "undocumented concept" is just not accurate, and so I don't see it
> as a valid reason to reject the patch.

I mean, I think it's pretty accurate. The fact that you can point to a
few uses of the terms "table rewrite" and "table scan" in the ALTER
TABLE documentation doesn't prove that those terms are defined there
or systematically discussed and it seems pretty clear to me that they
are not. And I don't even know what we're arguing about here, because
elsewhere in the same email you agree that it is reasonable to
critique the patch on the basis of how well it fits into the
documentation and at least for me that is precisely this issue.

I think the bottom line here is that you're not prepared to accept as
valid any opinion to the effect that we shouldn't commit these
patches. But that remains my opinion.

-- 
Robert Haas
EDB: http://www.enterprisedb.com



pgsql-hackers by date:

Previous
From: Tomas Vondra
Date:
Subject: Re: document the need to analyze partitioned tables
Next
From: Tom Lane
Date:
Subject: Re: [HACKERS] WIP aPatch: Pgbench Serialization and deadlock errors