LogicalDecode | Demo for PostgreSQL Logical Decoding with JDBC
kandi X-RAY | LogicalDecode Summary
kandi X-RAY | LogicalDecode Summary
LogicalDecode is a Java library typically used in Telecommunications, Media, Media, Entertainment applications. LogicalDecode has no bugs, it has no vulnerabilities, it has build file available, it has a Permissive License and it has low support. You can download it from GitHub.
It's useful to understand what physical replication is in order to understand logical decoding. Physical replication extends the functionality of recovery mode. Write Ahead Logs are written to disk before the actual database. These files contain enough information to recreate the transaction in the event of a catastrophic shutdown. In the event of an emergency shutdown (power fail, OOM kill) when the server comes back online it will attempt to apply the outstanding WAL up to the point of the shutdown. This is referred to as recovery mode. Physical replication takes advantage of this infrastructure built into the server. The standby is started in recovery mode and WAL created by the primary are applied to the standby. How that occurs is beyond the scope but you can read about it here . The interesting bit here is that we have a mechanism by which to access the changes in the heap without connecting to the database. There are a few caveats though which is where Logical Decoding comes to the rescue. First; WAL's are binary and their format is not guaranteed to be stable (in other words they can change from version to version) and second they contain changes for every database in the server. Logical decoding changes all of that by. Providing changes for only one database per slot Defining an API which facilitates writing an output plugin to output the changes in any format you define.
It's useful to understand what physical replication is in order to understand logical decoding. Physical replication extends the functionality of recovery mode. Write Ahead Logs are written to disk before the actual database. These files contain enough information to recreate the transaction in the event of a catastrophic shutdown. In the event of an emergency shutdown (power fail, OOM kill) when the server comes back online it will attempt to apply the outstanding WAL up to the point of the shutdown. This is referred to as recovery mode. Physical replication takes advantage of this infrastructure built into the server. The standby is started in recovery mode and WAL created by the primary are applied to the standby. How that occurs is beyond the scope but you can read about it here . The interesting bit here is that we have a mechanism by which to access the changes in the heap without connecting to the database. There are a few caveats though which is where Logical Decoding comes to the rescue. First; WAL's are binary and their format is not guaranteed to be stable (in other words they can change from version to version) and second they contain changes for every database in the server. Logical decoding changes all of that by. Providing changes for only one database per slot Defining an API which facilitates writing an output plugin to output the changes in any format you define.
Support
Quality
Security
License
Reuse
Support
LogicalDecode has a low active ecosystem.
It has 25 star(s) with 5 fork(s). There are 1 watchers for this library.
It had no major release in the last 6 months.
LogicalDecode has no issues reported. There are 1 open pull requests and 0 closed requests.
It has a neutral sentiment in the developer community.
The latest version of LogicalDecode is current.
Quality
LogicalDecode has 0 bugs and 0 code smells.
Security
LogicalDecode has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.
LogicalDecode code analysis shows 0 unresolved vulnerabilities.
There are 0 security hotspots that need review.
License
LogicalDecode is licensed under the BSD-3-Clause License. This license is Permissive.
Permissive licenses have the least restrictions, and you can use them in most projects.
Reuse
LogicalDecode releases are not available. You will need to build from source code and install.
Build file is available. You can build the component from source.
Installation instructions are not available. Examples and code snippets are available.
LogicalDecode saves you 99 person hours of effort in developing the same functionality from scratch.
It has 4598 lines of code, 531 functions and 7 files.
It has high code complexity. Code complexity directly impacts maintainability of the code.
Top functions reviewed by kandi - BETA
kandi has reviewed LogicalDecode and discovered the below as its top functions. This is intended to give you an instant insight into LogicalDecode implemented functionality, and help decide if they suit your requirements.
- Starts the process
- Convert a ByteBuffer to a String
- Checks if the replication slot is active
- Check if the server is compatible
- Insert changes in the database
- Wait for a replication slot
- Open replication connection
- Create a new logical replication slot
- Drops replication slot with the given name
- Creates the database URL
- Creates a database connection
- Returns the current log sequence number
- Parses a message
- Read a tuple
- Reads a string from the given buffer
- Converts a RowMessage to a String
- Converts the buffer into a string
- Create a publication table
- Drops publication
Get all kandi verified functions for this library.
LogicalDecode Key Features
No Key Features are available at this moment for LogicalDecode.
LogicalDecode Examples and Code Snippets
No Code Snippets are available at this moment for LogicalDecode.
Community Discussions
No Community Discussions are available at this moment for LogicalDecode.Refer to stack overflow page for discussions.
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install LogicalDecode
You can download it from GitHub.
You can use LogicalDecode like any standard Java library. Please include the the jar files in your classpath. You can also use any IDE and you can run and debug the LogicalDecode component as you would do with any other Java program. Best practice is to use a build tool that supports dependency management such as Maven or Gradle. For Maven installation, please refer maven.apache.org. For Gradle installation, please refer gradle.org .
You can use LogicalDecode like any standard Java library. Please include the the jar files in your classpath. You can also use any IDE and you can run and debug the LogicalDecode component as you would do with any other Java program. Best practice is to use a build tool that supports dependency management such as Maven or Gradle. For Maven installation, please refer maven.apache.org. For Gradle installation, please refer gradle.org .
Support
For any new features, suggestions and bugs create an issue on GitHub.
If you have any questions check and ask questions on community page Stack Overflow .
Find more information at:
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page