Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.Problem/Motivation
Non-public schema testing for Postgres appears to depend on the database configuration allowing on-the-fly schema creation or... something like that? Ensure the schema exists before testing it.
Steps to reproduce
Working on an issue that makes changes to code invoked by NonPublicSchemaTest::testIndex(). Went to re-create it locally and got:
Invalid schema name: 7 ERROR: schema "testing_fake" does not exist
Seems that there's something different about the pgsql server's configuration or whatever on CI vs. locally that allows for the non-standard schema name to be used on the fly.
Proposed resolution
Ensure the testing schema is present.
Remaining tasks
User interface changes
API changes
Data model changes
Release notes snippet
Issue fork drupal-3411403
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
- 3411403-pgsql-modules-nonpublicschematest
changes, plain diff MR !5980
Comments
Comment #3
bradjones1Comment #4
bradjones1I think this tracks to #1060476-110: Multiple issues when PostgreSQL is used with non-public schema - the CI pgsql environment has this schema already defined.
Comment #5
smustgrave commentedSince it's a test don't see any issue adding this line. And didn't seem to break anything leaning on that.
Comment #6
longwaveCommitted and pushed ebb73695b2 to 11.x and 285dc9cf53 to 10.2.x. Thanks!