> On Jan 24, 2020, at 10:43 AM, Robert Haas <robertmh...@gmail.com> wrote: > > Since 0001-0003 have been reviewed by multiple people and nobody's > objected, I have committed those. I think 0004-0005 have been reviewed and accepted by both me and Andrew, if I understood him correctly: > I've reviewed these patches and Robert's, and they seem basically good to me. Certainly, nothing in those two patches caused me any concern. I’m going to modify my patches as you suggested, get rid of the INSIST macro, and move the pg_wchar changes to their own thread. None of that should require changes in your 0004 or 0005. It won’t bother me if you commit those two. Andrew? — Mark Dilger EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
- Re: making the backend's json parser work in frontend ... Tom Lane
- Re: making the backend's json parser work in frontend ... David Steele
- Re: making the backend's json parser work in frontend ... Mark Dilger
- Re: making the backend's json parser work in frontend ... Alvaro Herrera
- Re: making the backend's json parser work in frontend ... Tom Lane
- Re: making the backend's json parser work in frontend ... Alvaro Herrera
- Re: making the backend's json parser work in frontend ... Mark Dilger
- Re: making the backend's json parser work in frontend code Andrew Dunstan
- Re: making the backend's json parser work in frontend code Robert Haas
- Re: making the backend's json parser work in frontend ... Mark Dilger
- Re: making the backend's json parser work in frontend ... Andrew Dunstan