Long lived Sinks seem to time out, pool doesn't seem to fix this automatically

[visch]

          > @BuzzCutNorman tried this PR here https://meltano.slack.com/archives/C01RKUVUG4S/p1688075229854589?thread_ts=1688060563.197079&cid=C01RKUVUG4S , I thought this would address an issue like

cur.execute(b''.join(parts)) cmd_type=elb consumer=True name=target-postgres producer=False stdio=stderr string_id=target-postgres
2023-06-29T20:23:10.757683Z [info     ] sqlalchemy.exc.OperationalError: (psycopg2.OperationalError) server closed the connection unexpectedly cmd_type=elb consumer=True name=target-postgres producer=False stdio=stderr string_id=target-postgres

By using Pooling properly but we're still hitting it. Going to take a look a bit deeper but wanted to capture this somewhere

@BuzzCutNorman can you try this again?

Originally posted by @visch in #153 (comment)

[BuzzCutNorman]

I did a meltano install --clean, target-postgres was pulled from the pipurl of git+https://github.com/MeltanoLabs/target-postgres.git@uppercase_alter_failure. It stopped with the following error when the second insert started.

psycopg2.OperationalError: server closed the connection unexpectedly 
     This probably means the server terminated abnormally 
     before or while processing the request.

[visch]

Sorry @BuzzCutNorman I didn't mean to ask you to do it yet again! I was just trying to capture this issue separately as obviously the fix I thought would make this work didn't work!