PgClientConfig title: PgClientConfig missing statement/query/lock timeouts and need for Migrator ...
Was it an intentional choice to exclude...
// number of milliseconds before a statement in query will time out, default is no timeoutstatementTimeout?: Duration.DurationInput | undefined,// number of milliseconds before a query call will timeout, default is no timeoutqueryTimeout?: Duration.DurationInput | undefined,// number of milliseconds a query is allowed to be en lock state before it's cancelled due to lock timeoutlockTimeout?: Duration.DurationInput | undefined,
// number of milliseconds before a statement in query will time out, default is no timeoutstatementTimeout?: Duration.DurationInput | undefined,// number of milliseconds before a query call will timeout, default is no timeoutqueryTimeout?: Duration.DurationInput | undefined,// number of milliseconds a query is allowed to be en lock state before it's cancelled due to lock timeoutlockTimeout?: Duration.DurationInput | undefined,
... from
PgClientConfig
PgClientConfig
?
I'm thinking that something like
transformClient
transformClient
might be extremely useful for forcing the
Migrator
Migrator
implementation to allow much higher timeouts (e.g.