| From: | "J(dot) Andrew Rogers" <jrogers(at)neopolitan(dot)com> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | PITR for replication? |
| Date: | 2004-04-02 00:58:28 |
| Message-ID: | 1080867508.29882.8.camel@localhost.localdomain |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-advocacy pgsql-hackers pgsql-hackers-pitr |
I may be completely missing the point here, but it looks to me as though
the PITR archival mechanism is also most of a native replication
facility. Is there anyone reason this couldn't be extended to
replication, and if so, is anyone planning on using it as such?
My memory is fuzzy on this point, but I seem to recall that this is
(was?) how replication is more-or-less done for many of the big
commercial RDBMS.
jrogers(at)neopolitan(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gavin Sherry | 2004-04-02 01:50:36 | Re: PITR for replication? |
| Previous Message | Rod Taylor | 2004-04-01 23:32:44 | Re: Aberdeen Study on OS RDBMS: exceprts and |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2004-04-02 01:12:23 | Re: Inconsistent behavior on Array & Is Null? |
| Previous Message | Joe Conway | 2004-04-01 23:50:26 | Re: Inconsistent behavior on Array & Is Null? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gavin Sherry | 2004-04-02 01:50:36 | Re: PITR for replication? |
| Previous Message | Chris Browne | 2004-04-01 19:42:05 | Re: Update on PITR |