From: | BladeOfLight16 <bladeoflight16(at)gmail(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Staging Database |
Date: | 2013-08-07 04:00:41 |
Message-ID: | CA+=1U=WK-K1Bfi0RkTcCbtZJ0aTcbFZ0E6cW5qM_-YpjN6qTrg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
The company I work for has a client who has expressed interest in having a
staging database for their data. Staging as in they add data, do some
QCing, then push to a database with an identical schema to make it public.
Fortunately, we're not doing that right now, but it's something they may
want later on. So I wanted to at least start thinking about it. What are
some ways of going about it? Some kind of replication set up comes to mind,
but it would need to be on demand, not constant. It also could be as
infrequent as quarterly, if that makes a difference. Preferably, it would
only require one server with PostgreSQL installed, but I'm not ruling out
multiple servers.
Thanks for any ideas.
From | Date | Subject | |
---|---|---|---|
Next Message | Albe Laurenz | 2013-08-07 06:56:21 | Re: inserting huge file into bytea cause out of memory |
Previous Message | ascot.moss@gmail.com | 2013-08-07 03:35:07 | Re: pg_stat_replication became empty suddenly |