The default values of some GUC parameters have been modified for better performance for modern hardware.

The native partition can be declared in clause statement of CREATE TABLE, which supports list, range and hash syntax.

Add lightdb_explain_no_runtime_pruned_partition parameter to control whether partitions pruned at runtime are shown in EXPLAIN ANALYZE output.

Built in pg_hint_plan, which can control execution plan with hinting phrases in comment of special form.

Built in pg_wait_sampling, which provides sampling based statistics of wait events.

Built in pg_profile, which can help you to find out most resource-consuming activities in your LightDB databases.

Built in pg_cron, a simple cron-based job scheduler that runs inside the database. It uses the same syntax as regular cron, but it allows you to schedule LightDB commands directly from the database.

Built in pg_cheat_funcs, which provides a set of cheat(but useful) functions on LightDB.

Built in pgfincore, which provides a set of functions to handle low-level management of relations using mincore to explore cache memory.

Built in orafce, an Oracle's compatibility functions and packages.

Built in pgaudit, which provides detailed session and/or object audit logging via the standard LightDB logging facility.

Built in pg_probackup, which manage backup and recovery of LightDB database clusters.

The following built-in extensions are auto enabled by default in every database(excepted dblink, pg_profile and pg_cron, which only available in postgres database), you don't need to perform CREATE EXTENSION manually.

Specially, a pg_cron job named "take_sample_every_10min" is also auto created by default only for postgres database, which call take_sample() provided by pg_profile extension every 10 minutes.