EuroLinux

EuroDB is primarily a proven PostgreSQL database engine

The heart of EuroDB is the PostgreSQL database engine. It has been developed via the Open Source methodology for more than 15 years. This refined product supports all common data types and provides support for storing large binary objects such as photos, music or videos. It also offers support for data types from NoSQL databases (JSON HSTORE). It has programming interfaces for many languages, including C/C++, Java™, Perl, Python, Ruby, Tcl, ODBC. PostgreSQL also includes excellent documentation that streamlines the process of system and application development.

EuroDB platform is an Enterprise-class solution. An integral part of it is professional technical assistance provided by certified architects and engineers.

The system supports such mechanisms as:

  • Schemas
  • Multiversion concurrency control
  • Point-in-time recovery
  • Tablespaces
  • Table partitioning
  • Replication
  • Nested transactions
  • Various backup methods
  • Advanced query planner to quickly diagnose performance issues
  • Acceleration of query execution by JIT compilation
  • Write-ahead log
  • International encoding sets
  • Multibyte character strings (mbstring)
  • Unicode.

EuroDB has been designed to support the most demanding applications.

EuroDB is fully compatible with PostgreSQL 11.4, 10.9, 9.6 and 9.5. Migration from the native implementation of this engine does not require any changes to the applications. Possible changes are simple, optional, and they aim to improve the use of the additional capabilities of EuroDB.

Maximum technical parameters of EuroDB:

Limit Value
Database size No limit
Table size 32TB
Row size 1.6TB
Field size 1GB
Rows per table No limit
Columns per table 250 – 1600 (depending on type)
Indices per table No limit

 

The advantages of the engine used by EuroDB include:

  • Data integrity protection mechanisms such as: compound primary keys, foreign keys, cascading updates and deletes, checking constraints, uniqueness constraints, non-empty field constraints
  • Support for retrieving partial results using the available index types
  • GiST indexing system that provides access to a wide range of sorting and searching mechanisms. The GiST extensions such as OpenFTS, which allows full text search and PostGIS, the database for geographical systems, make it versatile
  • Support for partitioning which significantly accelerates queries when tables contain very large data sets
  • Table inheritance making it possible to treat existing tables as base classes, allowing developers to use mechanisms known from object oriented programming languages
  • Rule sets allowing transformations of query types into different ones according to established rules
  • Support for efficient handling of JSON data with JSONB type and dedicated functions
  • Event-handling system that allows communication between clients (peer to peer) and client notifications of changes in the table.

The following table includes some features which illustrate the difference in the capabilities of the engine used in the EuroDB compared to the native PostgreSQL implementation available in Red Hat®, Oracle® Linux, CentOS, and Scientific Linux.

Feature RHEL/CentOS/SL/OL EuroDB
Maximum BLOB size 2GB 4TB
Modification of cluster configuration parameters
using a query (ALTER SYSTEM)
NO YES
Checksums of data files NO YES
COPY to STDIN/STDOUT NO YES
INSERT … ON CONFLICT DO NOTHING / UPDATE NO YES
Materialized views NO YES
Support for partitioning NO YES
JIT compilation of queries NO YES
Efficiency of GIN indices low high
Size of GIN indices large small

The full list of additional features is available here.

Feature RHEL/CentOS/SL/OL EuroDB
Maximum BLOB size 2GB 4TB
Modification of cluster configuration parameters
using a query (ALTER SYSTEM)
NO YES
Checksums of data files NO YES
COPY to STDIN/STDOUT NO YES
INSERT … ON CONFLICT DO NOTHING / UPDATE NO YES
Materialized views NO YES
Support for partitioning NO YES
JIT compilation of queries NO YES
Efficiency of GIN indices low high
Size of GIN indices large small
Modification of the login type for the table
(LOGGED / UNLOGGED)
NO YES
Private background processes NO YES
Dynamic background processes NO YES
Inheritance from foreign tables NO YES
Aggregation of data based on grouping sets
(GROUPING SET)
NO YES
Schema import from a foreign server NO YES
Enhanced JSON/JSONB support NO YES
Support for the LATERAL option
(access to the value of sub-queries in the parent query)
NO YES
Refreshing materialized views NO YES
Setting the minimum and maximum WAL size
(instead of the number of files)
NO YES
Parallel pg_dump (multithreaded) NO YES
Replication slots NO YES
Support for conflict-free, no-key column updates
(NO KEY UPDATE)
NO YES
Cascade replication NO YES
Anonymous shared memory NO YES
Fixed delay in replicas NO YES
Modifiable simple views (UPDATE/INSERT/DELETE) NO YES
Row numbering (WITH ORDINALITY) NO YES
Modifiable references to foreign databases
(Writable Foreign Data Wrapper)
NO YES
Abbreviated indices NO YES
pg_basebackup bandwidth control NO YES
BRIN indices NO YES
Parallel database cleaning (VACUUM) NO YES
Support for cold database start (pg_prewarm) NO YES
Reduced blocking level for table modifications NO YES
Table sampling (TABLESAMPLE) NO YES
Skipping blocked rows NO YES
Support for Kerberos 5 NO YES
Filter handling on aggregated results NO YES
Data transformation support (TRANSFORM) NO YES
pg_rewind (restoring cluster nodes after failover) NO YES
Support for regular expressions in trigram indexes NO YES
Access to a readable WAL dump NO YES
Support for defining partitions with primary keys, foreign keys, indices and triggers NO YES
Default partition for partitioned tables NO YES
Creating partitions using the so-called hash partitioning NO YES
Automatic transfer of rows between partitions in case of a key change NO YES
Menu
+48 22 243 22 33