On Fri, Aug 19, 2022 at 11:25:52AM -0700, Peter Geoghegan wrote:
> On Fri, Aug 19, 2022 at 9:40 AM Tom Lane wrote:
> > Yeah, we use "blocks" and "pages" interchangeably, which is something
> > I don't feel a need to change; but evidently the OP didn't realize that.
> > This is a job for the glossa
On Fri, Aug 19, 2022 at 9:40 AM Tom Lane wrote:
> Yeah, we use "blocks" and "pages" interchangeably, which is something
> I don't feel a need to change; but evidently the OP didn't realize that.
> This is a job for the glossary, perhaps?
I think that they're synonyms that can often (but not alway
Alvaro Herrera writes:
> On 2022-Aug-19, Bruce Momjian wrote:
>> Well, blocks and pages are the same size, so I don't see the problem.
> If you think about operating system "blocks" rather than Postgres
> "blocks", I can see how this can be interpreted differently. I'm not
> sure if this is a go
On 2022-Aug-19, Bruce Momjian wrote:
> On Fri, Aug 19, 2022 at 04:10:30AM +, PG Doc comments form wrote:
> > The following documentation comment has been logged on the website:
> >
> > Page: https://www.postgresql.org/docs/14/catalog-pg-class.html
> > Description:
> >
> > From source code, t
On Fri, Aug 19, 2022 at 04:10:30AM +, PG Doc comments form wrote:
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/14/catalog-pg-class.html
> Description:
>
> From source code, the relpage is the number of blocks. But, at the docu
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/14/catalog-pg-class.html
Description:
From source code, the relpage is the number of blocks. But, at the document,
it is written as Size of the on-disk representation of this table in pages
(