-
-
Notifications
You must be signed in to change notification settings - Fork 222
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
Add REPLICA MODE to the output of the isql SHOW DATABASE command #7425
Comments
Agreed about the replica mode. As for publication state, I'm not that sure. Multiple (named) publications will be allowed in future versions, with ALTER DATABASE managing only the default one (as a shortcut command). Why should we report status of the default publication but ignore the others? Replication may be working but you'll see it as inactive. I'd rather go for explicit |
Commands |
Should |
It should look something like the arguments to
|
Done re. the replica node, in v4 so far (to be frontported into v5 soon). As for SHOW PUBLICATION[S], I'll create a separate ticket. |
Isn't #7001 enough? |
Thanks for reminding. |
::: qa issues :::
|
Closing this ticket. Publication status will be covered separately by #7001. |
Aren't replica mode and publication status two separate things? Former is on target side of replication while later is in source. |
Yes, but I miss your point. Replica mode is already shown, thus this ticket is closed. #7001 is about publication status, it will be implemented (shown by ISQL) separately. SHOW DATABASE will print either "Replica mode" or "Publication" status strings (or both). |
Ah, sorry, I misread your comment. |
Now, to find out in what mode the current database is, one of the queries needs to be executed:
or
However, we have a nice SHOW DATABASE command in isql that shows a lot of things, but not the replication mode:
In addition, it would be nice to know if replication is enabled at all with the command:
What can be done with a request:
The text was updated successfully, but these errors were encountered: