Re: auto-sizing wal_buffers - Mailing list pgsql-hackers

From Robert Haas
Subject Re: auto-sizing wal_buffers
Date
Msg-id AANLkTimAzopJD5wHu354p47fN3AepoFvCoCG8=RF7-1+@mail.gmail.com
Whole thread Raw
In response to Re: auto-sizing wal_buffers  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: auto-sizing wal_buffers  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Sat, Jan 22, 2011 at 9:42 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Robert Haas <robertmhaas@gmail.com> writes:
>>> Oh, you're complaining about SetConfigOption, not the assign hooks.
>
>> I was actually complaining about the latter, and then switched gears
>> to the former.  I'm an equal-opportunity complainer today, I guess...
>
> It does strike me that we could provide SetConfigOptionInt,
> SetConfigOptionBool, and SetConfigOptionReal for the benefit of callers
> who'd prefer to pass values in those formats.  They'd still do sprintf
> internally, but this would make the call sites a bit cleaner.

Why do we need to double the conversion in the first place?

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Bug in pg_describe_object, patch v2
Next
From: Robert Haas
Date:
Subject: Re: Bug in pg_describe_object, patch v2