| From: | Christoph Moench-Tegeder <cmt(at)burggraben(dot)net> |
|---|---|
| To: | Igor Korot <ikorot01(at)gmail(dot)com> |
| Cc: | "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: CREATE TABLE fails |
| Date: | 2026-03-09 07:18:25 |
| Message-ID: | aa50QUXwEW_PWSvB@sciurus.exwg.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
## Igor Korot (ikorot01(at)gmail(dot)com):
> > 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
>
> Please check the PRIMARY KEY clause on that same linked page.
> It says "Storage Parameters" are definitely supported there.
As I wrote earlier: autovacuum_enabled is not a valid storage parameter
for indexes. The exact sentence after the one you're refering to tells
you that "Storage parameters for indexes are documented in CREATE INDEX"
and autovacuum_enabled is not documented there - it's valid for tables
only. (On the other hand, there are index storage parameters which are
not available for tables - they might make no sense on a table or refer
to specific index types only).
Regards,
Christoph
--
Spare Space.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Shaheed Haque | 2026-03-09 09:55:08 | Re: Unexpected deadlock across two separate rows, using Postgres 17 and Django's select_for_update() |
| Previous Message | jian he | 2026-03-09 03:48:26 | Re: Emitting JSON to file using COPY TO |