Skip to content

Added all of the remaining PostgreSQL messages#2

Merged
Hydrocharged merged 5 commits intomainfrom
daylon/mass-messages
Sep 22, 2023
Merged

Added all of the remaining PostgreSQL messages#2
Hydrocharged merged 5 commits intomainfrom
daylon/mass-messages

Conversation

@Hydrocharged
Copy link
Copy Markdown
Collaborator

This adds all of the remaining messages that were not added in #1.

@Hydrocharged Hydrocharged requested a review from zachmu September 21, 2023 12:14
Copy link
Copy Markdown
Member

@zachmu zachmu left a comment

Choose a reason for hiding this comment

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

Didn't look closely at this one, seems like a pretty straightforward extension of the previous PR

@Hydrocharged Hydrocharged changed the base branch from daylon/message-structure to main September 22, 2023 11:35
@Hydrocharged Hydrocharged merged commit 5f65ce1 into main Sep 22, 2023
@Hydrocharged Hydrocharged deleted the daylon/mass-messages branch September 22, 2023 11:35
codeaucafe added a commit to codeaucafe/doltgresql that referenced this pull request Dec 20, 2025
Remove skip list entries for tests that were previously panicking due
to a bug in go-mysql-server's index range building for OR conditions.
The bug occurred when OR conditions mixed indexed and non-indexed
columns (e.g., `SELECT * FROM t WHERE pk = 1 OR col = 1`).

The upstream fix in go-mysql-server PR dolthub#2136 appears to have resolved
this by properly handling OR conjunctions where non-indexed columns are
present, falling back to table scan instead of attempting an invalid
index lookup.

Tests removed from skip list:
- Complex Filter Index Scan dolthub#2
- Complex Filter Index Scan dolthub#3
- complicated range tree

All three tests now pass with the current go-mysql-server dep.

Refs: dolthub#1868
codeaucafe added a commit to codeaucafe/doltgresql that referenced this pull request Dec 20, 2025
Remove skip list entries for tests that were previously panicking due
to a bug in go-mysql-server's index range building for OR conditions.
The bug occurred when OR conditions mixed indexed and non-indexed
columns (e.g., `SELECT * FROM t WHERE pk = 1 OR col = 1`).

I believe the issue was fixed in PR dolthub#2123, which implemented a
LogicTreeWalker for DoltgreSQL that properly handles doltgres-specific
expression nodes when analyzing filters for index usage on OR
expressions.

Tests removed from skip list:
- Complex Filter Index Scan dolthub#2
- Complex Filter Index Scan dolthub#3
- complicated range tree

All three tests now pass.

Refs: dolthub#1868
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