On 2013-08-01 15:55:25 +0200, Dimitri Fontaine wrote:
> Greg Stark <stark@mit.edu> writes:
> > I think people are going to laugh at us if an open source database
> > software can't manage a simple flat file database of settings,
> > especially one that is purely write-only and can be a simple dump of
> > settings that are set by alter system.
Why would using a single-file solution imply that we cannot do the
other?
> So you say it's easier to implement per-GUC locking semantics correctly
> when using a single file with multiple units of information that all are
> of the same type? Interesting.
> Maybe the storage should actually be a shared catalog, in fact.
We can't read those early enough. Think a) of options that can only be
set at postmaster start b) think of crash recovery. We can't read the
catalog till we're in a consistent state.
Greetings,
Andres Freund
-- Andres Freund http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Training &
Services
