Brian C
                                            Brian C
                                        
                                    > The "describe prepared" is more difficult, because `Connection.prototype.parseMessage` is missing a case for the 't' (0x74 ParameterDescription). I thought I added that a while ago. I can add that...
@Yitzi2 can you provide a small code example demonstrating the problem?
Oh right - missed it! I was scanning for code-formatted text. To restate what @vitaly-t said & agree with his point: The connection parameters are resolved w/ a combo of...
Yeah pg=14
It looks like it's related to the lambda environment or something and not pg. [According to this](https://github.com/knex/knex/issues/3636#issuecomment-583225151) it's hitting both pg & mysql....which makes it somewhat unlikely to be caused...
Yah opening a new client every time is something you _can_ do, but the latency overhead of opening a client is aprox 20x the overhead of sending a query....so ideally...
that's perfect I'll get it looked at soon!
> I'm impressed with how quickly this is being looked at I've been _trying_ to work on `pg` at least 5 days a week this year. I'll be looking at...
:heart: thanks. Looking forward to making lots of folks node apps faster in the next few months when I do some work on perf! On Tue, Feb 25, 2020 at...
sure thing - pull request always welcome! On Wed, Feb 24, 2016 at 3:08 PM, Pavel Lang [email protected] wrote: > @brianc https://github.com/brianc Should I prepare pull request? My > suggestion...