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

Hi!
You're sure right about that! However, what do you
think about using triggers on update and insert from
two different machines, and then at night using cron
(rh linux) to call the other machine and
transfer/update only the records that have changed?

Although at this time the database only needs to be
active where I am, there will be about five other
people actively inputing/getting data from the server.

Initially, I was headed toward your second
proposal-until a quick calculation of the telephone
costs put it out of reach. Unfortunately, only one
office has decent internet connections other then by
phone line.

Thanks!
ajw

--- terry@greatgulfhomes.com wrote:
> Syncing the database will probably turn out to be a
> headache, you will
> always have to remember to do it upon arrival and
> before leaving, no matter
> how much of a rush you are in.
>
> There are better solutions:
>
> 1)  If you are the only person using the database,
> and noone is using it
> when you leave, why don't you just install it on a
> laptop and bring the
> laptop with you?
>
> 2)  You could also setup the database on a server in
> one of the offices, and
> make it accessible via the internet (this solution
> requres careful attention
> to security, don't use "trust"  use passwords, and
> enable TCP/IP access.
> This would require a static IP on your server.
>
> Terry Fielder
> Network Engineer
> Great Gulf Homes / Ashton Woods Homes
> terry@greatgulfhomes.com
>
>
>   -----Original Message-----
>   From: pgsql-general-owner@postgresql.org
> [mailto:pgsql-general-owner@postgresql.org]On Behalf
> Of Alan
>   Sent: Sunday, June 09, 2002 2:27 AM
>   To: pgsql-general@postgresql.org
>   Subject: [GENERAL] Help with data transfer please
>
>
>   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