-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Tue, 19 Feb 2008 15:22:42 -0300
Alvaro Herrera <alvherre@commandprompt.com> wrote:
> Joshua D. Drake wrote:
>
> > 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.
>
> That doesn't work, because many settings must be loaded before the
> database is fully operational.
Right but couldn't that be changed or if not, why not only have the
settings that "must" be loaded before the database is fully operation
in the postgresql.conf file.
I can hear the wails of we don't want multiple configuration sources
but we already have multiple configuration sources and having 90% of
the configuration in the database should would make it easier.
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)
iD8DBQFHux+nATb/zqfZUUQRAjJtAKCCaH8Ubud/OZ8Gv7oOAJf8jjO9nACfQFf8
WMzBcyZcNvWGgoPv6b1fR/w=
=IEBA
-----END PGP SIGNATURE-----