ns
       of the database configuration, rather than having a single large
       <TT
CLASS="FILENAME"
>postgresql.conf</TT
> file.  Consider a company that has two
       database servers, each with a different amount of memory.  There are likely
       elements of the configuration both will share, for things such as logging.
       But memory-related parameters on the server will vary between the two.  And
       there might be server specific customizations, too.  One way to manage this
       situation