From: | Josh Berkus <josh(at)agliodbs(dot)com> |
---|---|
To: | Jason Hihn <jhihn(at)paytimepayroll(dot)com>, Pgsql-Advocacy <pgsql-advocacy(at)postgresql(dot)org> |
Subject: | Re: Version Numbering |
Date: | 2002-12-13 03:08:37 |
Message-ID: | 200212121908.37519.josh@agliodbs.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-advocacy |
Jason,
> But I do know it will be no small deal for me when it is available, and
> don't I think I'm alone. I can see the headlines now: "PostgreSQL 8.0 - The
> best ORDBMS now available on Windows!"
This is *not* a discussion I want to have on Hackers. There are already
programmers on Hackers who aren't keen on the whole idea of an advocacy
group; asking them to change version numbers for marketing reasons would be
pouring gasoline on the fire.
> Then after that, all I need is a way to sync the row differences (insert,
> delete, updates only) since last sync. If I could 'play' a transaction log
> to one or more remote databases, then archive it, I'd be happy. Of course
> I'd need Win<->Unix compatibility, because remote machines would most likely
> be windows, and they'd be syncing to our unix master server. This is because
> most of our clients don't have a persistent link. They sync with us, we
> audit, fix, tally, and send it back. At the point of sending it down, all
> sites have consistency.
> Does something like this exist now? Right now we get all the data, for a few
> kilobytes of changes!
Point-in-time restore is a goal for 7.4. Whether this will extend to
log-based replication is beyond me.
--
-Josh Berkus
Aglio Database Solutions
San Francisco
From | Date | Subject | |
---|---|---|---|
Next Message | greg | 2002-12-13 13:55:54 | Re: Version Numbering |
Previous Message | Jason Hihn | 2002-12-12 22:18:15 | Version Numbering |