Josh Berkus wrote:
> Josh,
>
>
>>>My actual point was that we could put a lot of the options in a global
>>>table that could be adjusted versus having the flat file.
>
>
> You were aware of the virtual view pg_settings, right?

Yes and show all.

>
> I've considered before adjusting pg_settings so that it would take UPDATEs and
> convert them to SET statements. However, I'm not really sure what the
> benefit of this would be.

Well it wouldn't be unless it stuck from a reload or restart.

> As for making PostgreSQL.conf shorter, I'm personally always open to
> suggestions of settings which are useless and could be removed (backed by
> testing, of course). See our earlier discussion on commit_siblings.
>
> ANd if you think PostgreSQL is bad, you should see Oracle ...

Heh, I have. "

Sincerely,

Joshua D. Drake




--
Your PostgreSQL solutions company - Command Prompt, Inc. 1.800.492.2240
PostgreSQL Replication, Consulting, Custom Programming, 24x7 support
Managed Services, Shared and Dedicated Hosting
Co-Authors: plPHP, plPerlNG - http://www.commandprompt.com/

---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faq