From: PG Doc comments form <noreply@postgresql.org>
To: pgsql-docs@lists.postgresql.org
Cc: ray.hammond77@gmail.com
Subject: Table-space documentation
Date: Sun, 26 Nov 2023 21:41:48 +0000
Message-ID: <170103490808.398197.9036455918056934493@wrigleys.postgresql.org> (raw)
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/16/manage-ag-tablespaces.html
Description:
While reading the table-space documentation
https://www.postgresql.org/docs/16/manage-ag-tablespaces.html the
information I was looking for was not included. The page invites feedback,
so I though I would share. I was specifically looking for information on
maximum table-space size and whether there is a use-case in which you would
create several table-spaces to split your tables / indexes logically. I am
from an Oracle world and it is normal for me to think about creating
multiple table-spaces for groups of tables and placing a size on the
table-space so that space does not extend and fill the o/s disk-space. It
would be nice for the documentation to include information about this topic.
Even if it is says that these factors I should not worry about as postgres
handles them.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: noreply@postgresql.org, pgsql-docs@lists.postgresql.org, ray.hammond77@gmail.com
Subject: Re: Table-space documentation
In-Reply-To: <170103490808.398197.9036455918056934493@wrigleys.postgresql.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox