| From: | Philip Yarra <philip(dot)yarra(at)internode(dot)on(dot)net> |
|---|---|
| To: | elein <elein(at)varlena(dot)com> |
| Cc: | Devrim GUNDUZ <devrim(at)gunduz(dot)org>, slony1-general(at)gborg(dot)postgresql(dot)org, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [Slony1-general] Re: Slony RPM issue |
| Date: | 2005-10-06 00:46:10 |
| Message-ID: | 200510061046.10886.philip.yarra@internode.on.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, 6 Oct 2005 05:10 am, elein wrote:
> Generally a short sed (or perl if you like) script will fix
> these up. But it is really pretty obscure trail for people
> to find the exact problem.
Yeah, it's not that it's hard to fix when you know where to look, but my aim
is to produce a site installation checklist for other people to follow. The
simpler it is, the better the chance of it being successful.
I'd prefer a site installation to be:
- install PostgreSQL RPMs
- unpack our specific postgresql.conf and pg_hba.conf
- set up database from scripts
- install Slony RPM
- unpack our specific slony config files
- run minimal commands to get Slony going
- profit! (or at least I don't get woken up by phone calls at 3am)
That's why I'm so keen on the RPMs working out of the box, with minimal need
for post-installation tweaks/fixes.
Regards, Philip.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Philip Yarra | 2005-10-06 00:59:27 | Re: Slony RPM issue |
| Previous Message | Steinar H. Gunderson | 2005-10-06 00:12:39 | Re: [HACKERS] A Better External Sort? |