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.

Sign up for GitHub

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

Jump to bottom

Prefer platform specific memory barriers #708

Merged
merged 3 commits into from Jul 6, 2018
Merged

Prefer platform specific memory barriers #708

merged 3 commits into from Jul 6, 2018

Commits on May 8, 2018

  1. Prefer platform specific memory barriers 

    Following the wisdom of postgres, we opt to use platform specific memory barriers when available. These are generally more performant. In this PR, we add specific cases for i386, x86_64.

In the future, we could look at using pg's atomics library directly: https://github.com/postgres/postgres/tree/9d4649ca49416111aee2c84b7e4441a0b7aa2fac/src/include/port/atomics
    @ianks
    ianks committed May 8, 2018
    Copy the full SHA
    d715dff View commit details
    Browse the repository at this point in the history

  2. Remove HAVE_GCC_SYNC flag

    @ianks
    ianks committed May 8, 2018
    Copy the full SHA
    5afd748 View commit details
    Browse the repository at this point in the history

Commits on Jul 6, 2018

  1. Add note about new memory bariers

    @pitr-ch
    pitr-ch committed Jul 6, 2018
    Copy the full SHA
    e43ad71 View commit details
    Browse the repository at this point in the history