Date: Sun, 8 Mar 2026 23:29:35 +0100
From: Christoph Moench-Tegeder <cmt@burggraben.net>
To: Igor Korot <ikorot01@gmail.com>
Cc: "pgsql-generallists.postgresql.org" <pgsql-general@lists.postgresql.org>
Subject: Re: CREATE TABLE fails
Message-ID: <aa34T0Tr3hdPCywt@elch.exwg.net>
References: <CA+FnnTyGEM-1mwxKPbwFTOodf+YUX=TxTmBPY5S=Yh1h=oVY9A@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <CA+FnnTyGEM-1mwxKPbwFTOodf+YUX=TxTmBPY5S=Yh1h=oVY9A@mail.gmail.com>
User-Agent: Mutt/2.3.0 (2026-01-25)
Archived-At: <https://www.postgresql.org/message-id/aa34T0Tr3hdPCywt%40elch.exwg.net>
Precedence: bulk

## Igor Korot (ikorot01@gmail.com):

> [quote]
> draft=# CREATE TABLE leagues_new(id serial, name varchar(100),
> drafttype smallint, scoringtype smallint, roundvalues smallint,
> leaguetype char(5), salary integer, benchplayers smallint, primary
> key(id) INCLUDE (drafttype, scoringtype) WITH( fillfactor = 50,
> autovacuum_enabled ));
> ERROR:  unrecognized parameter "autovacuum_enabled"
> [/quote]
> 
> But the page at
> https://www.postgresql.org/docs/16/sql-createtable.html#SQL-CREATETABLE-STORAGE-PARAMETERS
> says it's available.

It's available as a TABLE storage parameter, but you put it on the index
definition (where it's not valid) - this could be a conceptual mistake
or a misplaced right parenthesis.
See the example on your linked page:
https://www.postgresql.org/docs/16/sql-createtable.html#SQL-CREATETABLE-STORAGE-PARAMETERS:~:text=fill%20factor%20for%20both%20the%20table%20and%20its%20unique%20index

Regards,
Christoph

-- 
Spare Space