Custom Postgres schema breaks followers about eventsourcing

[lxop]

Actually, I've just found that using .replace(".", "_") can cause non-unique statement names. This is because statement names are truncated at 63 characters (by default, at least) because they are an identifier. Putting the schema name first chews up valuable real-estate. Since statements are local to a session, would the schema name actually be necessary? If not, .split(".")[-1] might be more appropriate.

[johnbywater]

@lxop As discussed on Slack, thanks for raising this issue.

I think I fixed both aspects in 88fe8bb.

Let me know if it's working for you now? Please note, since this issue was raised, I have changed several things in the postgres module, especially adding a connection pool which still needs more work. In the meantime, please set environment variables 'POSTGRES_POOL_MIN_CONN' and 'POSTGRES_POOL_MAX_CONN' to a suitable number.

[johnbywater]

@lxop I have finished the new connection pool. As documented, the new names for the environment variables mentioned above are POSTGRES_POOL_SIZE and POSTGRES_MAX_OVERFLOW. See also POSTGRES_POOL_TIMEOUT.