pg.ddx.io pgsql-docs@postgresql.org mailing list archive
help / color / mirror / Atom feedTable-space documentation
3+ messages / 3 participants
[nested] [flat]
* Table-space documentation
@ 2023-11-26 21:41 PG Doc comments form <noreply@postgresql.org>
0 siblings, 2 replies; 3+ messages in thread
From: PG Doc comments form @ 2023-11-26 21:41 UTC (permalink / raw)
To: pgsql-docs@lists.postgresql.org; +Cc: ray.hammond77@gmail.com
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.
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: Table-space documentation
@ 2023-11-27 13:21 David G. Johnston <david.g.johnston@gmail.com>
parent: PG Doc comments form <noreply@postgresql.org>
1 sibling, 0 replies; 3+ messages in thread
From: David G. Johnston @ 2023-11-27 13:21 UTC (permalink / raw)
To: ray.hammond77@gmail.com <ray.hammond77@gmail.com>; pgsql-docs@lists.postgresql.org <pgsql-docs@lists.postgresql.org>
On Sunday, November 26, 2023, PG Doc comments form <noreply@postgresql.org>
wrote:
> 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.
>
We tend to avoid documenting things that don’t exist. So the lack of a
documented limit or any syntax to define one means no limit exists.
As for usage patterns, there is a note I thought (maybe wiki FAQ?) that
since the only thing you get with a tablespace is another root level
storage place having more than one per disk really serves no purpose.
David J.
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: Table-space documentation
@ 2023-11-27 18:54 Laurenz Albe <laurenz.albe@cybertec.at>
parent: PG Doc comments form <noreply@postgresql.org>
1 sibling, 0 replies; 3+ messages in thread
From: Laurenz Albe @ 2023-11-27 18:54 UTC (permalink / raw)
To: ray.hammond77@gmail.com; pgsql-docs@lists.postgresql.org
On Sun, 2023-11-26 at 21:41 +0000, PG Doc comments form wrote:
> 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.
There is no maximum tablespace size, other than the size of the filesystem
the tablespace is on.
In 99% of all cases, don't create a tablespace in PostgreSQL. Just use
the default tablespace.
In a virtualized environment, don't ever create a tablespace.
Tablespaces were more important back what people had physical boxes
with physical disks of limited size.
There are still some use cases, but they are extremely rare.
Yours,
Laurenz Albe
^ permalink raw reply [nested|flat] 3+ messages in thread
end of thread, other threads:[~2023-11-27 18:54 UTC | newest]
Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2023-11-26 21:41 Table-space documentation PG Doc comments form <noreply@postgresql.org>
2023-11-27 13:21 ` David G. Johnston <david.g.johnston@gmail.com>
2023-11-27 18:54 ` Laurenz Albe <laurenz.albe@cybertec.at>
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