Dynamically setting the schema in pg-promise still warns about duplicate database objects - pg-promise

Question

I have a database that has several different schemas, like a multi-tenant architecture, in Postgres 9.5.7.
I've followed the example in this answer to dynamically set the schema for particular queries. All of the context is encapsulated in a class and as far as I can tell I'm calling pgp in the correct way, but I still get the WARNING: Creating a duplicate database object for the same connection. error.
I have a configuration initializer like so:
// initializer.js
const initOptions = {
schema(name) {
return name ? name : 'public'
}
}
const _config = {
host: process.env.DBSERVER || nconf.get('database:server') || 'localhost',
port: process.env.DBPORT || nconf.get('database:port') || '5432',
user: process.env.DBUSER || nconf.get('database:user') || 'dev',
password: process.env.DBPASS || nconf.get('database:password') || 'pass1234',
database: process.env.DBNAME || nconf.get('database:user') || process.env.DBUSER || 'dev'
}
const pgp = require('pg-promise')(initOptions)
// default database
const pgdb = pgp(_config)
module.exports = {
pgp
, pgdb
, _config
}
And the class using it like so:
const { pgp, _config } = require('../db/initializer')
class Tenant {
constructor(name) {
this.name = name
this.db = pgp(_config, name)
}
async getMetadata() {
try {
const data = await this.db.many(`SELECT * FROM versions`)
return data
} catch (err) {
log.error(`Error getting versions for ${this.name}:`, err)
return null
}
}
}
The stack trace from this warning points to this line in the _config:
host: process.env.DBSERVER || nconf.get('database:server') || 'localhost',
I'm creating a bunch of these classes all at once and on-demand