Skip to content

docs: document timestamp interval parameters#36870

Open
petrosagg wants to merge 1 commit into
MaterializeInc:mainfrom
petrosagg:document-timestamp
Open

docs: document timestamp interval parameters#36870
petrosagg wants to merge 1 commit into
MaterializeInc:mainfrom
petrosagg:document-timestamp

Conversation

@petrosagg
Copy link
Copy Markdown
Contributor

@petrosagg petrosagg commented Jun 2, 2026

Closes CLU-32

Closes CLU-32

Signed-off-by: Petros Angelatos <petrosagg@gmail.com>
@petrosagg petrosagg requested a review from a team as a code owner June 2, 2026 13:53
`client_encoding` | `UTF8` | The client's character set encoding. The only supported value is `UTF-8`. | Yes
`client_min_messages` | `notice` | The message levels that are sent to the client. <br/><br/> Accepts values: `debug5`, `debug4`, `debug3`, `debug2`, `debug1`, `log`, `notice`, `warning`, `error`. Each level includes all the levels that follow it. | Yes
`datestyle` | `ISO, MDY` | The display format for date and time values. The only supported value is `ISO, MDY`. | Yes
`default_timestamp_interval` | `1s` | The interval at which timestamps are assigned to data ingested from sources and tables. New sources are created with this value unless overridden by the `TIMESTAMP INTERVAL` option of [`CREATE SOURCE`](/sql/create-source/) or [`ALTER SOURCE`](/sql/alter-source/). Accepts positive [interval](/sql/types/interval/) values (e.g. `'500ms'`, `'1s'`). Changing this parameter does not affect existing sources. | [Contact support]
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Only for emphasis, maybe make the last sentence (?):

his setting applies only when creating sources; changing it does not affect existing sources.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also ... I see how we updated the legacy create source syntax. For the new syntax, can you not override this value?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants