Typo in Storage Parameter

Started by PG Bug reporting formabout 1 month ago3 messagesdocs
Jump to latest
#1PG Bug reporting form
noreply@postgresql.org

The following documentation comment has been logged on the website:

Page: https://www.postgresql.org/docs/18/sql-createtable.html
Description:

```text
STORAGE { PLAIN | EXTERNAL | EXTENDED | MAIN | DEFAULT }

This form sets the storage mode for the column. This controls whether
this column is held inline or in a secondary TOAST table, and whether the
data should be compressed or not. PLAIN must be used for fixed-length values
such as integer and is inline, uncompressed. MAIN is for inline,
compressible data. EXTERNAL is for external, uncompressed data, and EXTENDED
is for external, compressed data. Writing DEFAULT sets the storage mode to
the default mode for the column's data type. EXTENDED is the default for
most data types that support non-PLAIN storage. Use of EXTERNAL will make
substring operations on very large text and bytea values run faster, at the
penalty of increased storage space. See Section 66.2 for more information.
```
In the 2nd to last section it uses `bytea` instead of `bytes`

#2Daniel Gustafsson
daniel@yesql.se
In reply to: PG Bug reporting form (#1)
Re: Typo in Storage Parameter

On 22 Oct 2026, at 20:10, PG Doc comments form <noreply@postgresql.org> wrote:

In the 2nd to last section it uses `bytea` instead of `bytes`

It is referring to te bytea datatype, see https://www.postgresql.org/docs/18/datatype-binary.html

--
Daniel Gustafsson

#3Joshua Carlson
jrcarl624@gmail.com
In reply to: Daniel Gustafsson (#2)
Re: Typo in Storage Parameter

Thanks for the clarification.

—
Joshua Carlson

Get Outlook for iOS<https://aka.ms/o0ukef>
________________________________
From: Daniel Gustafsson <daniel@yesql.se>
Sent: Friday, 23 October 2026 04:14:56
To: jrcarl624@gmail.com <jrcarl624@gmail.com>; pgsql-docs@lists.postgresql.org <pgsql-docs@lists.postgresql.org>
Subject: Re: Typo in Storage Parameter

On 22 Oct 2026, at 20:10, PG Doc comments form <noreply@postgresql.org> wrote:

In the 2nd to last section it uses `bytea` instead of `bytes`

It is referring to te bytea datatype, see https://www.postgresql.org/docs/18/datatype-binary.html

--
Daniel Gustafsson