Repository navigation
PostgreSQL: Support ALTER TABLE ... RESET and storage parameters without a value - #2744
Open
LucaCappelletti94 wants to merge 2 commits into
Open
LucaCappelletti94 wants to merge 2 commits into
LucaCappelletti94 wants to merge 2 commits into
Conversation
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #2744 +/- ##
==========================================
+ Coverage 82.60% 82.62% +0.01%
==========================================
Files 42 42
Lines 35607 35629 +22
Branches 35607 35629 +22
==========================================
+ Hits 29414 29438 +24
- Misses 2659 2661 +2
+ Partials 3534 3530 -4 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
LucaCappelletti94
force-pushed
the
upstream/alter-table-reset-bare-reloptions
branch
6 times, most recently
from
October 29, 2026 12:29
b2477c0 to
0047cdb
Compare
sabir-akhadov-localstack
approved these changes
Oct 29, 2026
| AlterTableOperation::SetUnlogged | ||
| } else if self.parse_keyword(Keyword::RESET) { | ||
| self.expect_token(&Token::LParen)?; | ||
| let options = self.parse_comma_separated(Parser::parse_identifier)?; |
Contributor
There was a problem hiding this comment.
ALTER TABLE t RESET (toast.autovacuum_enabled) fails with Expected: ), found: .; PostgreSQL 16 accepts it (ALTER TABLE). Vec<ObjectName> via parse_object_name(false) would cover the toast. prefix; SET (toast.autovacuum_enabled = false) has the same limitation through parse_sql_option, which is pre-existing.
Contributor
Author
There was a problem hiding this comment.
Fixed, thank you for pointing this out.
LucaCappelletti94
force-pushed
the
upstream/alter-table-reset-bare-reloptions
branch
3 times, most recently
from
October 30, 2026 10:56
ea5489c to
862076a
Compare
LucaCappelletti94
force-pushed
the
upstream/alter-table-reset-bare-reloptions
branch
from
October 30, 2026 14:36
f0693e0 to
cbf416f
Compare
LucaCappelletti94
force-pushed
the
upstream/alter-table-reset-bare-reloptions
branch
from
October 30, 2026 17:40
cbf416f to
3e9551b
Compare
LucaCappelletti94
force-pushed
the
upstream/alter-table-reset-bare-reloptions
branch
from
October 30, 2026 19:13
3e9551b to
ff54037
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
ALTER TABLE t RESET (fillfactor)fails withExpected: ADD, RENAME, PARTITION, SWAP, DROP, REPLICA IDENTITY, SET, or SET TBLPROPERTIES after ALTER TABLE, found: RESET, and a storage parameter named without a value, as inCREATE VIEW v WITH (security_invoker) AS SELECT 1orALTER TABLE t SET (autovacuum_enabled), fails withExpected: =. PostgreSQL documentsRESET ( storage_parameter [, ... ] )forALTER TABLEand reads a storage parameter given without a value astrue.RESETparses into a newAlterTableOperation::ResetOptionsholding the parameter names, the shape #2730 uses forALTER VIEW ... RESET. A key with no=after it parses to the existingSqlOption::Identbehind a newDialect::supports_sql_option_without_value, which PostgreSQL and Generic enable, so the other dialects still report the missing=. PostgreSQL's grammar also accepts a bare key inCREATE TEXT SEARCHoptions, so the negative test there now runs on the dialects without the flag.