• Reference
  • Version · 6.0
  • Change Automation Reference

dbclhistory-capture-extensions

Last updated: August 12, 2026

--dbclhistory-capture-extensions is a global Boolean parameter that specifies whether Liquibase captures information about installed extensions in the DATABASECHANGELOGHISTORY table. It is available in Liquibase 4.27.0 and later. The default value is true.

Uses

Liquibase comes pre-installed with some common database drivers to make it easier for you to deploy changes quickly. You can also install more extensions to add more database support, such as the liquibase-mongodb extension. By default, Liquibase records the filepath and name of all Liquibase extensions you have installed in the DATABASECHANGELOGHISTORY (DBCLH) table.

However, if you want to exclude extension information from your DBCLH, you can set --dbclhistory-capture-extensions to false.

Syntax

You can set this parameter in the following ways:

Option

Syntax

Liquibase properties file (defaults file)

liquibase.dbclhistory.captureExtensions: <true|false>

Global flow file argument

globalArgs: { dbclhistory-capture-extensions: "<true|false>" }

Global CLI parameter

liquibase --dbclhistory-capture-extensions=<true|false> update --changelog-file=example-changelog.xml

JVM system property (JAVA_OPTS environment variable)

Unix:

JAVA_OPTS=-Dliquibase.dbclhistory.captureExtensions=<true|false>

Windows:

JAVA_OPTS=-D"liquibase.dbclhistory.captureExtensions"=<true|false>

Liquibase environment variable

LIQUIBASE_DBCLHISTORY_CAPTURE_EXTENSIONS=<true|false>

PreviousdateNextdbclhistory-capture-sql