From: | Samuel Smith <pgsql(at)net153(dot)net> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Postgres architecture for multiple instances |
Date: | 2015-02-23 02:53:06 |
Message-ID: | 54EA9612.80408@net153.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 02/21/2015 05:25 PM, David Steele wrote:
> On 2/21/15 6:08 PM, Adrian Klaver wrote:
>>
>> Currently the built in replication solutions work at the cluster level,
>> not at the database level. There are third party tools, Slony and
>> Bucardo come to mind, that can work at a more focused level.
>
> Again, it depends in what kind of access your customers have to the
> database. Logical backups can be done on a per-database basis (and are
> very practical for small datasets), but physical backups (which are more
> efficient) must backup the entire cluster (except for the third-party
> solutions noted above that have their own challenges).
>
> You said you don't want to give a lot of information, but the optimal
> solution depends on how your customers connect to their database:
>
> 1) Entirely through an application or API
> 2) Directly to the db via psql, PgAdmin, JDBC, etc.
>
> Without that information it's hard to give really solid advice.
>
Sorry, to be more specific our application is on top of a java
framework. Similar to Ruby On Rails. Customers don't interface with the
database at all, only through the website which provides our services.
--Sam
From | Date | Subject | |
---|---|---|---|
Next Message | Gavin Flower | 2015-02-23 03:29:05 | Re: Postgres architecture for multiple instances |
Previous Message | Eric Hanson | 2015-02-22 21:17:37 | Re: [GENERAL] express composite type literal as text |