Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PostgreSQL Optimizer Methodology #1

Open
zhjwpku opened this issue Aug 5, 2024 · 7 comments
Open

PostgreSQL Optimizer Methodology #1

zhjwpku opened this issue Aug 5, 2024 · 7 comments
Labels
archived The workshop has finished, but you can still post your questions

Comments

@zhjwpku
Copy link
Member

zhjwpku commented Aug 5, 2024

Workshop Title

Robert Haas, CMU Database Group, PostgreSQL Optimizer Methodology

Date: August 2024

Resources

@zhjwpku zhjwpku added the ongoing This is the workshop for current month label Aug 5, 2024
@zhjwpku zhjwpku changed the title August 2024: Robert Haas, CMU Database Group, PostgreSQL Optimizer Methodology Robert Haas, CMU Database Group, PostgreSQL Optimizer Methodology Aug 5, 2024
@zhjwpku zhjwpku changed the title Robert Haas, CMU Database Group, PostgreSQL Optimizer Methodology PostgreSQL Optimizer Methodology Aug 5, 2024
@zhjwpku
Copy link
Member Author

zhjwpku commented Aug 8, 2024

@zhjwpku
Copy link
Member Author

zhjwpku commented Aug 8, 2024

In Unconference - Stream 2 - 13:15-14:15 - PGCon 2022

There is a discussion on adding schetches for MCV inter-column estimation.

@zhjwpku
Copy link
Member Author

zhjwpku commented Aug 8, 2024

Some advice from Richard Guo on hacking optimizer:

  1. read the README thoroughly
  2. use git blame to see the commit message about a specific code block
  3. the bottom line for adding some optimizer rules is not introduce performance regression

@zhjwpku
Copy link
Member Author

zhjwpku commented Aug 8, 2024

Question:

Why PostgreSQL does not have a vector execution engine[1], there seems to be some efforts happened on hacker list, but goes no where.

Answer:

Supporting vector execution engine will require significant work for both the optimizer and executor.

[1] https://www.postgresql.org/message-id/flat/CAB0yrem3PYu2qQD4%3DJOg8y_5QAK%2BQ%2BK5yEptxs0t71j5cRyoOQ%40mail.gmail.com

@zhjwpku
Copy link
Member Author

zhjwpku commented Aug 8, 2024

Here are some questions asked in the session, but I could not summarize the answers:

  1. Is there any infrasture that can help detecting performance regression from optimizer feature?
  2. Is there any extra considerations when it comes to Partitioned tables?
  3. Somebody mentioned GP orca in the message chat, no specific question.

@zhjwpku
Copy link
Member Author

zhjwpku commented Aug 17, 2024

@zhjwpku
Copy link
Member Author

zhjwpku commented Aug 29, 2024

PostgreSQL Hacking Workshop - August 2024 summarized by Andreas Scherbaum @andreasscherbaum

@zhjwpku zhjwpku added archived The workshop has finished, but you can still post your questions and removed ongoing This is the workshop for current month labels Aug 29, 2024
zhjwpku added a commit that referenced this issue Aug 31, 2024
Signed-off-by: Junwang Zhao <[email protected]>
zhjwpku added a commit that referenced this issue Aug 31, 2024
Signed-off-by: Junwang Zhao <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
archived The workshop has finished, but you can still post your questions
Projects
None yet
Development

No branches or pull requests

1 participant