Re: Re: [COMMITTERS] pgsql: pgbench: Allow the transaction log file prefix to be changed.

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Re: [COMMITTERS] pgsql: pgbench: Allow the transaction log file prefix to be changed.
Date: 2016-11-10 03:12:10
Message-ID: CAB7nPqTXhvbgMhSvPGgj4MDZnYDG14Fcqm1dXQ_yE6aL4AJQ0g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

On Thu, Nov 10, 2016 at 12:08 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
>> On Wed, Nov 9, 2016 at 4:51 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>>> Perhaps the "logpath" buffer that the filename is constructed in
>>> needs to be made bigger. 64 bytes was obviously enough with the
>>> old pattern, but it's not with the new.
>
>> Oops, yes, that seems like a good idea. How about 64 -> MAXPGPATH?
>
> If we want to stick with the fixed-size-buffer-on-stack approach,
> that would be the thing to use. psprintf is another possibility,
> though that would add a malloc/free cycle.

MAXPGPATH is used quite a lot in the binaries of src/bin/, just using
that seems fine to me.. My 2c.
--
Michael

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Robert Haas 2016-11-10 04:17:00 Re: Re: [COMMITTERS] pgsql: pgbench: Allow the transaction log file prefix to be changed.
Previous Message Tom Lane 2016-11-10 03:08:06 Re: Re: [COMMITTERS] pgsql: pgbench: Allow the transaction log file prefix to be changed.

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Geoghegan 2016-11-10 03:18:56 Re: Parallel tuplesort (for parallel B-Tree index creation)
Previous Message Tom Lane 2016-11-10 03:08:06 Re: Re: [COMMITTERS] pgsql: pgbench: Allow the transaction log file prefix to be changed.