| From: | Emanuel Calvo Franco <postgres(dot)arg(at)gmail(dot)com> |
|---|---|
| To: | mark(dot)lehmann(at)gmail(dot)com |
| Cc: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: Optimal Flexible Architecture or Optimal Configuration Layout for Postgres |
| Date: | 2009-06-26 15:09:35 |
| Message-ID: | f205bb120906260809l58e82009oef76f2392a52d430@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
2009/6/25 Mark Lehmann <mark(dot)lehmann(at)gmail(dot)com>:
> I have been looking for a best practices layout for Postgres.
>
> The Centos and Debian distros configure the files for Postgres in different
> places. Neither of them seem to put the files in ideal locations for
> multiple instance administration on the same or different machines. Has
> someone already created a best practice for placing pg_xlogs, regular logs,
> data, indexes, binary code, and configuration files onto the filesystem?
>
I like Centos configuration. :)
Honestly i didn't see something like you describe, but it'll very cool
write a kind
of 'best admin practices'. In the wiki i found some of tuning (is the
most similar that
i found).
Want to add a page on the wiki and we add things little by little?
Just sugestion,
what do you think?
--
Emanuel Calvo Franco
ArPUG [www.arpug.com.ar] / AOSUG Member
www.emanuelcalvofranco.com.ar
| From | Date | Subject | |
|---|---|---|---|
| Next Message | donghe | 2009-06-26 16:29:51 | Re: PHP cann't access to postgres databse |
| Previous Message | Ankur Sam | 2009-06-26 11:38:46 | Restricting administrator's DB access |