| From: | Rich Jones <miserlou(at)gmail(dot)com> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Request for Code Review: BPGSQL |
| Date: | 2016-02-11 13:06:10 |
| Message-ID: | CADJYzxJ2JZ-G0cs-pL-5Hp8DSBpBo1gu2O4-Yq9g2-R_hZ2A9g@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hello, team!
I am writing on behalf of the BPGSQL Project [1] to request a code audit
from a core PGSQL team member.
The current maintainer is worried about the security of the code, and is
considering closing the project unless it can be properly reviewed [2]. As
a project living downstream[3] of that client library, I'd obviously much
rather see that project get reviewed rather than see it die.
Would anybody here be so kind as to volunteer to give BPGSQL a code review
from an upstream developer's perspective? It would have a lot of value
downstream users who want to use Postgres on Amazon RDS for serverless
applications, and I'm sure in plenty of other places.
Thanks very much!,
Rich Jones
[1] https://github.com/d33tah/bpgsql
[2] https://github.com/d33tah/bpgsql/issues/7
[3] https://github.com/Miserlou/django-zappa/issues/3
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Teodor Sigaev | 2016-02-11 13:11:37 | Re: Fuzzy substring searching with the pg_trgm extension |
| Previous Message | Thom Brown | 2016-02-11 12:40:56 | max_parallel_degree context level |