Hi.
Thinking about this issue, I wonder if it wouldn't be easier to have
FusionForge use its own PostGreSQL cluster instead of the default one ('main')
which is created by postgres upon installation.
Why not use pg_createcluster to create a dedicated cluster for it ?
Maybe this is completely naive suggestion, as I'm not really competent in
PostGres matters.
What's your opinion ?
Best regards,
On Sat, Nov 14, 2009 at 06:49:34AM +0100, Olivier Berger wrote:
>
> Upon installation of fusionforge 4.8.1 on testing, one is prompted (every
> time ?) with UCF about conflicting changes on
> /etc/postgresql/8.3/main/pg_hba.conf :
> "A new version of configuration file /etc/postgresql/8.3/main/pg_hba.conf is
> available, but the version installed currently has been locally modified."
>
> This is really not intuitive and would need to be non-ambiguous.
>
> In the installation test I'm doing, the postgres installation is made as a
> dependency of it, so no prior configuration was made by the user. Then,
> pg_hba.conf is what it should be right after postgres-8.3 has installed it.
> So there has been no user configuration.
>
> The default option prompted by UCF is to keep the installed version, however,
> by looking at the diffs, it seems that the best thing to do might be to
> install the new version with additions made by gforge-db-postgresql's
> postinst.
>
> Is UCF used the right way ? Ain't it another way to deal with such cases when
> no one made any modifications and the postinst's version can be applied
> safely ?
>
> Thanks in advance.
>
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
