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

pg12 compatibility related changes #222

Merged
merged 7 commits into from
Feb 17, 2020
Merged

pg12 compatibility related changes #222

merged 7 commits into from
Feb 17, 2020

Conversation

mtuncer
Copy link
Member

@mtuncer mtuncer commented Feb 17, 2020

  • fix the build
  • revisit data file naming method. (use the old logic in pre-pg12)

@mtuncer mtuncer changed the title {WIP} pg12 compatibility related changes pg12 compatibility related changes Feb 17, 2020
Oid databaseOid = relationFileNode.dbNode;
Oid relationFileOid = relationFileNode.relNode;

Oid databaseOid = MyDatabaseId;
StringInfo cstoreFilePath = makeStringInfo();
appendStringInfo(cstoreFilePath, "%s/%s/%u/%u", DataDir, CSTORE_FDW_NAME,
Copy link
Collaborator

Choose a reason for hiding this comment

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

Will there need to be upgrade instructions for this?

Copy link
Member Author

Choose a reason for hiding this comment

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

behavior is the same as long as you stay in the same PG version. We never officially supported upgrading PG. So we should be fine there

@mtuncer mtuncer merged commit da737b2 into develop_v1x Feb 17, 2020
@mtuncer mtuncer deleted the pg12_compat branch February 17, 2020 18:53
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