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

Why restart_lsn but not confirmed_flush_lsn ? #4

Open

Andrewpqc opened this issue Jan 10, 2021 · 0 comments

Labels

question

Andrewpqc commented Jan 10, 2021

https://github.com/ihippik/wal-listener/blob/261cd6e0e8fda777ee7b9e5f76069a2e5486c4a6/listener/repository.go#L19、

restart_lsn：
The address (LSN) of oldest WAL which still might be required by the consumer of this slot and thus won't be automatically removed during checkpoints.

confirmed_flush_lsn：
The address (LSN) up to which the logical slot's consumer has confirmed receiving data. Data older than this is not available anymore. NULL for physical slots.

If it is possible to lead to repeat message when use restart_lsn?

ihippik added the question label

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment