| From: | Magnus Hagander <magnus(at)hagander(dot)net> |
|---|---|
| To: | Brian Weaver <cmdrclueless(at)gmail(dot)com> |
| Cc: | Marko Tiikkaja <pgmail(at)joh(dot)to>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Patch: incorrect array offset in backend replication tar header |
| Date: | 2012-09-27 22:20:43 |
| Message-ID: | CABUevExXH+r2A2-uQ220h4duPkU5=6quOpAhhMB=yS-t0D8tnw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Sep 28, 2012 at 12:12 AM, Brian Weaver <cmdrclueless(at)gmail(dot)com> wrote:
> Magnus,
>
> I probably just did a poor job of explaining what I wanted to try. I
> was going to have the base backup open two connections; one to stream
> the tar archive, the second to receive the wal files like
> pg_receivexlog.
This is what --xlog=stream does.
> The wal files received on the second connection would be streamed to a
> temporary file, with tar headers. Then when the complete tar archive
> from the first header was complete received simply replay the contents
> from the temporary file to append them to the tar archive.
Ah, yeah, that should also work I guess. But you could also just leave
the the data in the temporary tarfile the whole time. IIRC, you can
just cat one tarfile to the end of another one, right?
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2012-09-27 22:30:25 | Re: Patch: incorrect array offset in backend replication tar header |
| Previous Message | Brian Weaver | 2012-09-27 22:18:36 | Re: Patch: incorrect array offset in backend replication tar header |