Re: doc: create table improvements - Mailing list pgsql-hackers

From Laurenz Albe
Subject Re: doc: create table improvements
Date
Msg-id 83766e536155461b0e19514436fd3fbaa8e4c6a0.camel@cybertec.at
Whole thread Raw
In response to Re: doc: create table improvements  (Chao Li <li.evan.chao@gmail.com>)
List 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



pgsql-hackers by date:

Previous
From: Bertrand Drouvot
Date:
Subject: Re: relfilenode statistics
Next
From: Xuneng Zhou
Date:
Subject: Re: Optimize SnapBuildPurgeOlderTxn: use in-place compaction instead of temporary array