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

README: add a notice on the unsupported REPLICATION IDENTITY FULL #69

Closed
wants to merge 1 commit into from

Conversation

chtitux
Copy link

@chtitux chtitux commented Jan 6, 2017

@PJMODOS
Copy link
Contributor

PJMODOS commented Jan 18, 2017

The text is not completely correct, PKey is needed only when adding to replication sets that replicate updates and deletes, insert only replication sets will have no problem with table without PK.

@PJMODOS
Copy link
Contributor

PJMODOS commented Jan 18, 2017

I think in reality just the "PRIMARY KEY or REPLICA IDENTITY required" section needs to be update to not refer to just REPLICA IDENTITY but to REPLICA IDENTITY index.

@chtitux chtitux closed this Oct 25, 2017
@chad-earthscope
Copy link

I think in reality just the "PRIMARY KEY or REPLICA IDENTITY required" section needs to be update to not refer to just REPLICA IDENTITY but to REPLICA IDENTITY index.

+1

Current docs say:
"... PRIMARY KEY or other valid replica identity such as a UNIQUE constraint."

Perhaps I should have been able to figure out that REPLICA IDENTITY FULL did not necessarily qualify as a UNIQUE constraint. Would be appreciated to more explicitly define what would qualify as a "valid replica identity".

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.

None yet

3 participants