Re: Isolated databases or instances
| От | Tom Lane |
|---|---|
| Тема | Re: Isolated databases or instances |
| Дата | |
| Msg-id | 7692.1171660568@sss.pgh.pa.us обсуждение |
| Ответ на | Re: Isolated databases or instances (Scott Marlowe <smarlowe@g2switchworks.com>) |
| Ответы |
Re: Isolated databases or instances
|
| Список | pgsql-admin |
Scott Marlowe <smarlowe@g2switchworks.com> writes:
> On Fri, 2007-02-16 at 13:18, Henry, Nigel, CYFD wrote:
>> We are at the beginning of the building of a 3-tier
>> development/test/uat environment. We would like some advice on how
>> the PostgreSQL database should be configured for this environment.
> What exactly are you trying to accomplish with multiple PostgreSQL
> instances here? I can't see there being any great advantage to three
> separate instances than having three discrete databases defined in one
> instance.
Separating development and production instances seems perfectly sensible
to me. For instance, if your development code triggers a crash in
Postgres, you don't really want that event to take out your production
sessions. Also, you might want to run Postgres version x+1 for awhile
as development before replacing version x for production.
regards, tom lane
В списке pgsql-admin по дате отправления: