Re: Help with data transfer please - Mailing list pgsql-general

Hi!
This guy was really creative! Unfortunately, only one
of the offices has a decent internet connection--the
other only a telephone line. My initial program
construction was to use a postgre-apache-php setup on
rh linux using telephone connections. AT&T would make
this to costly at three to four hours of user
long-distance charges. I'm thinking of perhaps adding
triggers to each of the files based on update or
insert and perhaps writing a program executed from
cron that will on a nigthly basis update two different
machines via telephone--it would be relatively quick.
What do you think?

Thanks,
ajw

--- "Peter A. Daly" <petedaly@ix.netcom.com> wrote:
> This isn't really the answer you are looking for,
> but I have seen it
> done in the past.
>
> Discouraged by the lack of cost effective high speed
> phone lines in
> northern New York State, a guy started up his own
> small ISP.  He
> couldn't afford a leased line for his little
> venture.  He purchased a
> total of 12 phone lines.  4 in the area he wanted to
> have access from, 4
> in Syracuse, were he could get cost effective
> internet access, and 4
> "dummy phone lines" half way between.  The 4 phone
> lines in the middle
> had regional calling access to both other ends, at
> flat rate.  He set
> each of the 4 phone lines in the middle to do call
> forwarding to the 4
> phone lines in syracuse.  With 8 modems, and a
> little fancy networking,
> he was able to setup a 134.4 baud "always on"
> connection from "the
> sticks" to "the big city" at a rock bottom price.
>
> You may only need one end to end line (3 lines
> total) in your situation.
>  Another solution may be a small VPN between your
> two locations.  If you
> have "flat rate" internet service in both locations,
> set up a little 2
> node virtual private network betweeen them.
>
> Sorry I don't have any answers at the Postgres
> level, I hope others may.
>  I could come up with some, but none that I could
> see being reliable,
> other than maybe having the DB on a removable hard
> disk, and taking it
> with you (which may not be such a bad solution after
> all.)
>
> Hope this helps,
>
> -Pete
>
> Alan wrote:
>
> > Hi All!
> >
> > I don't know if this is the right place to post
> this, but if anyone
> > knows databases-you all do!
> >
> >
> >
> > In brief, I'm open to suggestions to the cheapest
> most reliable way of
> > either maintaining two seperate postgre servers or
> of using one server
> > from an office 30 miles away.
> >
> >
> >
> > The long version:
> >
> > I have my postgre database running smoothly in my
> rural office, (
> > i.e., only telephone connections to the office).
> I'm about to open a
> > second office 30 miles away that does not
> currently have internet
> > access, but could. I will be alternating offices
> on an every other day
> > basis and it is important the the information in
> the "database" goes
> > with me so my staff can update it where I am.
> However, although I've
> > now written the internent programs necessary to
> access the single
> > database (currently in the rural office), AT&T
> will be more then happy
> > to charge a small fortune to maintain telephone
> connection (long
> > distance) between the two offices. Since I'm
> initially expecting zero
> > income from the new office, it is not feasible at
> this time to be
> > calling the rural office via telephone due to
> telephone costs. Also, I
> > might add, no-one will be in the rural office
> durring the time that I
> > am in the new office. The database uses many
> sequences for record
> > uniqueness. Thus simply transporting the new or
> modified records (via
> > floppy) would leave the sequences corrupted (I
> think??).
> >
> >
> >
> > I'm sure this has been solved many thousand of
> times before, can
> > someone please suggest a simple (cheap) solution?
> >
> >
> >
> > Thanks,
> >
> > ajw
> >
>
>
>


__________________________________________________
Do You Yahoo!?
Yahoo! - Official partner of 2002 FIFA World Cup
http://fifaworldcup.yahoo.com