agentsclimarketplace

Bitrix postgresql

Skill bxmaximum/bitrix-framework-skills/skills/bitrix-postgresql

Covers PostgreSQL support in Bitrix — PgsqlConnection, migration from MySQL, compatible code, module support matrix. Applied when configuring or migrating to PostgreSQL Enterprise editions. Key terms — PostgreSQL, PgsqlConnection, migration, compatible-code.From its SKILL.md

Install
npx -y skills add bxmaximum/bitrix-framework-skills --skill bitrix-postgresql

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 19 stars19 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.8 KB, 611 tokens by cl100k_base, as published. Nobody here has run it

PostgreSQL in Bitrix

Baseline: main 23.0+. Supported in Enterprise for PostgreSQL licenses (B24 and CMS). Connection class: \Bitrix\Main\DB\PgsqlConnection.

Configuration

'connections' => [
    'value' => [
        'default' => [
            'className' => \Bitrix\Main\DB\PgsqlConnection::class,
            'host' => 'localhost',
            'database' => 'bx',
            'login' => 'bx',
            'password' => '***',
            'options' => \Bitrix\Main\DB\Connection::DEFERRED,
        ],
    ],
    'readonly' => true,
],

Before Migration

  1. Obtain Enterprise for PostgreSQL license (test key available for 6 months).
  2. Update Performance Monitor module to 24.0.0+.
  3. Project must use UTF-8 encoding.
  4. Close site to visitors during migration.
  5. Test on staging first — return to MySQL after production PostgreSQL launch requires manual work.

Module Compatibility

Not all kernel and marketplace modules support PostgreSQL. Incompatible modules are disabled during conversion wizard.

Check custom code:

  • MySQL-specific SQL (LIMIT syntax differences handled by SqlHelper, but raw SQL may break).
  • MySQL install scripts under install/mysql/ or install/db/mysql/ need matching PostgreSQL scripts under install/pgsql/ or install/db/pgsql/.

Find modules missing pgsql install:

for mysql in bitrix/modules/*/install/mysql/install.sql bitrix/modules/*/install/db/mysql/install.sql; do
  pgsql=$(echo $mysql | sed 's#/mysql/#/pgsql/#')
  test -e $pgsql || echo "missing: $pgsql"
done

Check kernel module install folders: each supporting module should have matching install/pgsql/ or install/db/pgsql/ scripts. Inspect bitrix/modules/<module>/install/ in the project.

Migration Methods

  1. Wizard — Admin conversion tool (lists disabled modules on step 1).
  2. CLI — manual server-side migration via Performance Monitor module tools.

Writing Compatible Code

  • Use ORM and SqlHelper — avoid MySQL-specific functions in raw SQL.
  • Use SqlExpression placeholders instead of string concatenation.
  • Test DDL in both MySQL (install/mysql/ or install/db/mysql/) and PostgreSQL (install/pgsql/ or install/db/pgsql/) if the module supports both.
  • Avoid ENGINE=InnoDB, backticks-specific syntax, UNSIGNED.

Checklist

  • License is Enterprise for PostgreSQL.
  • All custom modules checked for pgsql install scripts.
  • Raw SQL audited for MySQL-specific syntax.
  • Migration tested on copy before production.
  • Marketplace modules verified with vendors.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.