On Aug 12, 2008, at 2:43 PM, Greg Smith wrote:
On Tue, 12 Aug 2008, Bruce Momjian wrote:
There's already some changes needed in this area needed to
execute the
full GUC cleanup/wizard plan that's being worked on. The
pg_settings view
really should show the value both as the user input it and as
it's stored
internally for cases like these, which lowers the confusion here
a bit
even without going so far as converting everything to bytes.
Is this a TODO?
I don't think you need yet another TODO for every detail, the
existing TODO "Add external tool to auto-tune some postgresql.conf
parameters" has to squash a bunch of issues in this area. This
particular issue Greg raised will already be improved significantly
if executing the larger project plan at http://wiki.postgresql.org/
wiki/GUCS_Overhaul
Yeah, but OTOH it's not clear at all when we might see such a tool,
while clarifying this stuff would help people immediately... I think
a TODO would be good to make sure this doesn't fall through the cracks.
--
Decibel!, aka Jim C. Nasby, Database Architect [EMAIL PROTECTED]
Give your computer some brain candy! www.distributed.net Team #1828
smime.p7s
Description: S/MIME cryptographic signature
