Skip to content

Generic: Preserve ONLY as an unquoted table name (#3003) - #3004

Open
blaginin wants to merge 1 commit into
apache:branch-0.64from
blaginin:db/backport-only-0.64
Open

blaginin wants to merge 1 commit into
apache:branch-0.64from
blaginin:db/backport-only-0.64

Conversation

@blaginin

Copy link
Copy Markdown
Member

Backport #3003 to the 0.64 release line.

(cherry picked from commit 97afe81)

Backport to the 0.64 release line.

(cherry picked from commit 97afe81)
@blaginin blaginin self-assigned this Nov 18, 2026
@blaginin
blaginin changed the base branch from main to branch-0.64 November 18, 2026 21:30
@github-actions

Copy link
Copy Markdown

No dialect label was applied because the title does not name a SQL dialect.

If this change targets one or more dialects, edit the title to <Dialect>[, <Dialect>]: <description>, add a Dialects: <Dialect>[, <Dialect>] line to the description, or reply with one. Reply Dialects: none if the change is dialect-agnostic.

Changed files touch PostgreSQL.

@LucaCappelletti94

Copy link
Copy Markdown
Contributor

LGTM, but I do not have the keys to the kingdom when it comes to backporting.

cc @alamb do we have a procedure for it?

@blaginin

Copy link
Copy Markdown
Member Author

@alamb

alamb commented Nov 19, 2026

Copy link
Copy Markdown
Contributor

I don't know if we have ever done a patch release from this repo.

I would personally suggest we just do a new major release . Maybe we can move this one up

The per-release overhead is the same either way

@alamb

alamb commented Nov 19, 2026

Copy link
Copy Markdown
Contributor

If we are happy to do a new major release, I can put it on my list for next week

@blaginin

Copy link
Copy Markdown
Member Author

If we are happy to do a new major release, I can put it on my list for next week

i will make sure there are no other regressions for datafusion by then and do release prep

@LucaCappelletti94

Copy link
Copy Markdown
Contributor

If we are happy to do a new major release, I can put it on my list for next week

I would say that we still have to finalize quite a few PRs before the next major.

@blaginin does this PR constitute something that needs to be urgently fixed? If so proceeding with a cherrypicked fix as a patch may be the best way forward, and avoid a major release.

Unrelated PS: my brain is really not appreciating the new scrambled PR UI

@alamb

alamb commented Nov 19, 2026

Copy link
Copy Markdown
Contributor

I would say that we still have to finalize quite a few PRs before the next major.

What is waiting to be finalized and why? What if we made a release now (like next week) and in December?

Unrelated PS: my brain is really not appreciating the new scrambled PR UI

Agreed it is taking some time to get used to

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.

3 participants