Re: doc: create table improvements

Laurenz Albe <laurenz.albe@cybertec.at>

From: Laurenz Albe <laurenz.albe@cybertec.at>
To: Chao Li <li.evan.chao@gmail.com>
Cc: "David G. Johnston" <david.g.johnston@gmail.com>, Peter Eisentraut <peter@eisentraut.org>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>, jian he <jian.universality@gmail.com>
Date: 2025-12-16T10:25:16Z
Lists: pgsql-hackers
On Tue, 2025-12-16 at 10:14 +0800, Chao Li wrote:
> > On Oct 23, 2025, at 12:43, Laurenz Albe <laurenz.albe@cybertec.at> wrote:
> > <v4-0001-Unclutter-CREATE-TABLE-synopsis.patch>
> 
> Overall the change looks good to me. I have only one comment about the naming
> of “oversize_storage”. Why not just “storage_parameters” or similar that
> sounds more straightforward?

"Storage parameter" is not a good idea, because we use that term for
something else: CREATE TABLE ... WITH (storage_parameter = value)

I think "oversize_storage" expresses well what is regulated here.
I'm open to "toast_options" or similar as an alternative, but I think
it might be better to avoid jargon - not everybody reading that page
will be familiar with the term.

Yours,
Laurenz Albe