Mathieu Rochette

it's true that you can guarantee the query to be executed first, *but*, only if the connect callback is synchronous, if your callback uses await/promises before issuing the query, the...

well there is [the undocumented `options.verify`](https://github.com/brianc/node-pg-pool/blob/277dc508daea03a8f6c0bcc3c534cab5b2501b12/index.js#L235) that could be used for on `connect`, but it won't work for `acquired`: `options.verify` is only called for new clients and not when they...

it's a websocket application, I call `select set_config('session.id', $1::text, false)` with the session id corresponding to socket I'm working with (it's used by row level security rules)

well, the problem is that the project name is not known in the docker-compose.yml. the project name default to the folder name and can be changed at run time (eg:...

oh, I guess you mean `FILTER_LABEL` instead of `IGNORE_LABEL` ?

here is a new version which accepts `FILTER_LABEL=com.some.label:labelvalue` (value is optional). if `FILTER_LABEL` is not set and `IGNORE_DOCKER_COMPOSE_PROJECT` is not `true` it tries to set a `FILTER_LABEL` to match only...

suppose I have 4 containers: - c1.1, with label `com.docker.compose.project` = `p1` - c1.2, with label `com.docker.compose.project` = `p1` - c2.1, with label `com.docker.compose.project` = `p2` - c3.1, with label...

@lalyos Indeed, at least changing `:` to `=` seems reasonable, I'll do that soon

I've updated the the PR to use `=` instead of `:` @progrium what do you think about what is being said about filtering events ? I could support `FILTER_BY=label=` &...

I’m not using this anymore so I don’t really have the time to update the PR. however I’ve allowed maintainers to edit the PR. and otherwise anyone willing to do...