James Dixon

@592da we ended up using a custom Node 8 runtime, which has worked for us. Not ideal but we didn't have the time or resources to dig deep into this...

@briandamaged you're correct on the stack trace pointing to the `pg` client. Seems like someone else opened up a similar issue here: https://github.com/brianc/node-postgres/issues/2112 ``` Error: select * from "appointment" where...

Do you guys have any thoughts about why this would be present with Node 10 / 12 but not Node 8?

> @jamesdixon this has been around as long as AWS lambda with pg has existed. @elhigu I'm not sure what you're referring to specifically? There has definitely been a behavior...

@592da I'm not sure why using a Node 8 runtime isn't working for you. It resolved the issue immediately for me. Can you verify that in the AWS console that...