-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Tue, 19 Feb 2008 15:36:26 +0100
Magnus Hagander <magnus@hagander.net> wrote:
> Currently, pgAdmin supports editing postgresql.conf remotely using the
> adminpack to open the file, change it locally in memory, and using the
> adminpack again to write it back. This means that in theory pgAdmin
> needs a full postgresql.conf parser. Right now it doesn't have this -
> it just exposes the config file itself. Which sucks for usability,
> and it's something I've heard a lot of people complain about. Other
> databases (in my personal experience MSSQL, but IIRC I've had people
> say the same about other ones as well) support configuring the
> database remotely (and using a GUI for the most common options), and
> this is a feature that a lot of users are lacking in PostgreSQL. I'd
> like to do something about that.
>
>
> What I'd really like to see is something like a new keyword on the SET
> command, so you could to SET PERMANENT foo=bar, which would write the
> configuration back into postgresql.conf.
IMO this should all be in the database and that's it. The idea that our
global settings are in a file seems unusual consider we have a
perfectly good storage engine available.
Sincerely,
Joshua D. Drake
- --
The PostgreSQL Company since 1997: http://www.commandprompt.com/
PostgreSQL Community Conference: http://www.postgresqlconference.org/
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL SPI Liaison | SPI Director | PostgreSQL political pundit
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFHuxvEATb/zqfZUUQRAhoFAJ4jDcM0WyUuu0VgN9EZL7qRmMPPSACfb7Gh
dyY7w3KDaCO1xQMdhtF50x0=
=6/GJ
-----END PGP SIGNATURE-----
