Re: [SL] Postgres replication

[<la...@cl...>]

Dear Dr.

Yes, we do need the data near real time and it seems that Postgres is
currently working on a readable hot standby so if you can wait may be it
is a good idea to deploy the readable hot standby when it is available. We
are probably going to head down the direction of Slony-I and there is a
catch with it as it does require the replicated tables to have a primary
key. That probably shouldn't be an issue as it may be alright to add a
primary key if there isn't one by the way of composite pirmay key or just
plain adding a new column.

BTW, as for the steps there are more then a few...

http://slony.info/documentation/

Regards,

Tim

> With sufficient bandwidth it'll be trivial to pg_dump every hour or even
> more often. But that does not solve the issue of having access to the
> invoice data in real time.
>
> ANd, I don't think setting someting up is overkill because you only
> do it once. Unless of course the learning curve is very steep and/or
> the overhead is large.
>
> If someone comes up with a plan, please publish the cookbook on how
> to do it :-)-O
>
> MySQL has got this feature too, hasn't it?
>
> el
>
> on 5/28/08 3:27 PM Adam Vandemore said the following:
>> la...@cl... wrote:
>>> hello all...our business has now the need to replicate our sl/postgres
>>> db
>>> from our main office in ca to ny as the ny system (public and outside
>>> of
>>> our firewall) has the need to generate non-critical read only invoice
>>> and
>>> inventory reports. our requirements are real simple and slony-i seems
>>> to
>>> be an overkill. we have also evaluated pgpool-ii but it was ruled out
>>> as
>>> it doesn't support x509 ssl connection (a must for business data).
>>> oralce
>>> and informix would have been nice as they both provide standby
>>> read-only
>>> databases that are very simple to manage. it is too bad that you cannot
>>> access a standby postgres database.
>>>
>>> so my question is anyone has any comments on what other tools out there
>>> that may allow us to create a postgres standby read-only database? if
>>> nothing we may just have to walk down the slony-i path...thanks ahead
>>> for
>>> any comments.
>>>
>>> regards,
>>>
>>> tim
>> If you go the route you intent on, I'd guess slony is your best option.
>> Of course there are other ways to do this too, like manually scripting a
>> db export import daily.
>>
>> However with knowing just the info you provided, setting up a
>> master-slave itself seems like overkill.  What about a VPN?  Or setting
>> up SL on it's own host?  My SL server isn't sharing it's IP with other
>> domains, so for me a default to deny firewall covers virtually all my
>> security needs.  You can always run SSL on it if you like.
>>
>
> --
> Dr. Eberhard W. Lisse  \        / Obstetrician & Gynaecologist (Saar)
> el...@li... el108-ARIN / *     |   Telephone: +264 81 124 6733 (cell)
> PO Box 8421             \     /   Please do NOT email to this address
> Bachbrecht, Namibia     ;____/        if it is DNS related in ANY way
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> sql-ledger-users mailing list
> sql...@li...
> https://lists.sourceforge.net/lists/listinfo/sql-ledger-users
>