On 2020-Mar-10, Michael Paquier wrote: > On Tue, Mar 10, 2020 at 01:05:40PM +0300, Alexander Korotkov wrote: > > Two options seem reasonable to me in this case. The first is to pass > > length as additional argument as you did. The second option is to > > make argument a pointer to fixed-size array as following.
Another option is to return the command as a palloc'ed string (per psprintf), instead of using a caller-stack-allocated variable. Passing the buffer len is widely used, but more error prone (and I think getting this one wrong might be more catastrophic than a mistake elsewhere.) This is not a performance-critical path enough that we *need* the optimization that avoids the palloc is important. (Failure can be reported by returning NULL.) Also, I think the function comment could stand some more detailing. Also, I think Msvcbuild.pm could follow Makefile's ideas of one line per file. Maybe no need to fix all of that in this patch, but let's start by adding the new file it its own line rather than reflowing two adjacent lines (oh wait ... does perltidy put it that way? if so, nevermind.) -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
