Skip to content

Fix Windows Access Violation error during collector start up #7

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

Merged
merged 1 commit into from
Mar 5, 2018
Merged

Fix Windows Access Violation error during collector start up #7

merged 1 commit into from
Mar 5, 2018

Conversation

asp437
Copy link
Contributor

@asp437 asp437 commented Mar 5, 2018

Since address space layout may vary on Windows due to processes creation procedure, it is not safe to configure entry point via pointer to the function.

@funbringer
Copy link
Collaborator

@asp437 why don't we use this approach in older releases?

@ildus ildus merged commit 1ab3270 into postgrespro:master Mar 5, 2018
@asp437
Copy link
Contributor Author

asp437 commented Mar 5, 2018

@funbringer if you mean older releases of Postgres, after the patch it will use this approach for any version on Windows, not only PG10.

@funbringer
Copy link
Collaborator

@asp437 Just in case didn't get the idea: we don't need the other branch of this macro at all. We could get rid of the code that won't be of any use.

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