cartodb4/Windshaft-cartodb
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Ensure all pg connections are being refreshed

Browse Source
This commit is contained in:
Daniel García Aubert 2018-11-06 12:17:39 +01:00
parent 4d1ed0be27
commit f3b1bb742a
3 changed files with 1265 additions and 384 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1640
package-lock.json generated
View File

File diff suppressed because it is too large Load Diff

2
test/acceptance/user-database-timeout-limit.js
View File

@ -576,7 +576,7 @@ describe('user database timeout limit', function () {
});
});
describe.skip('torque', function () {
describe('torque', function () {
describe('while validating in layergroup creation', function () {
beforeEach(function (done) {
const mapconfig = createMapConfig({

5
test/support/test-client.js
View File

@ -1267,6 +1267,11 @@ TestClient.prototype.setUserDatabaseTimeoutLimit = function (timeoutLimit, callb
const dbuser = _.template(global.environment.postgres_auth_user, { user_id: 1 });
const publicuser = global.environment.postgres.user;
// IMPORTANT: node-postgres uses internallly a singleton, to refresh all pull connections
// you need to ensure that your dependency tree has only one working version of `cartodb-psql` & `node-postgres`
// if not, test using this function cannot ensure that all connections have the new settings (STATEMENT_TIMEOUT)
//
// TODO: upgrade to node-postgres@7.x
const psql = new PSQL({
user: 'postgres',
dbname: dbname,