pg2k4j not working correctly on PostgreSQL version 11.x about pg2k4j

[teej]

@rkass Thanks for taking a look! I’ll take a crack at trying to repro the issue with test cases.

[rkass]

Hi @teej thanks for submitting. We have used pg2k4j with postgres 10 databases so it's interesting to hear about your experiences with version 11. Since we're not yet using pg 11 we haven't had the opportunity to observe the issue you describe.

I did create this pr https://github.com/disneystreaming/pg2k4j/pull/28/files which introduces integration tests with version 11 of postgres. For now the tests passed as is (same recipe for db version 10 and 11), but if you could add tests that break with db version 11 and not db version 10 that'd go a long way to discovering if there is a problem and hunting down a fix.

[Tybot204]

For what it's worth, I have pg2k4j working with pg 11.5. It's possible < pg 11.5 had an issue that has since been resolved? Either that or some config is causing the issue in particular.

I setup pg2k4j following the README verbatim with the following setup:

• PG 11.5 running in AWS RDS (no public accessibility)
• EKS running in the same VPC
• pg2k4j running as a stand alone deployment in Kubernetes
  • Options set include awsaccesskey, awssecret, pgdatabase, pghost, pgpassword, pguser, region, and streamname