Re: CREATE TABLE fails
Igor Korot <ikorot01@gmail.com>
From: Igor Korot <ikorot01@gmail.com>
To: Ron Johnson <ronljohnsonjr@gmail.com>, "pgsql-generallists.postgresql.org" <pgsql-general@lists.postgresql.org>
Date: 2026-03-08T23:55:40Z
Lists: pgsql-general
Ron, On Sun, Mar 8, 2026 at 6:48 PM Ron Johnson <ronljohnsonjr@gmail.com> wrote: > > On Sun, Mar 8, 2026 at 7:41 PM Igor Korot <ikorot01@gmail.com> wrote: >> >> David, >> >> On Sun, Mar 8, 2026 at 6:37 PM David G. Johnston >> <david.g.johnston@gmail.com> wrote: >> > >> > On Sunday, March 8, 2026, Igor Korot <ikorot01@gmail.com> wrote: >> >> >> >> >> >> >> >> >> >> But the page at >> >> >> https://www.postgresql.org/docs/16/sql-createtable.html#SQL-CREATETABLE-STORAGE-PARAMETERS >> >> >> says it's available. >> >> >> >> >> >> What am I missing? >> > >> > >> > Those are table storage parameters. >> > >> >> >> >> primary >> >> key(id) INCLUDE (drafttype, scoringtype) WITH( fillfactor = 50, >> >> autovacuum_enabled = on )); >> >> ERROR: unrecognized parameter "autovacuum_enabled" >> >> draft=# >> > >> > >> > You are specifying index storage parameters here. >> > >> > The first paragraph of your linked section says: >> > >> > “Storage parameters for indexes are documented in CREATE INDEX.” >> > >> > You will find autovacuum_enabled is not listed there. Because you can’t vacuum an index separately from its table. >> >> So I will have to compare the CREATE INDEX page with this one and >> figure out which one is supported where? > > > Well, yes. Why should you be shocked that some storage parameters just aren't relevant to indices. I am, because they are documented as such according to the note I mentioned in the email above, quoting the "WITH " clause explanation. Thank you. > > -- > Death to <Redacted>, and butter sauce. > Don't boil me, I'm still alive. > <Redacted> lobster!