Quick Links

Re: Add pg_basebackup single tar output format

From:	Joshua Elsasser <josh(at)idealist(dot)org>
To:	pgsql-hackers(at)postgresql(dot)org
Subject:	Re: Add pg_basebackup single tar output format
Date:	2015-09-29 22:16:22
Message-ID:	1443564988-17928-1-git-send-email-josh@idealist.org
Views:	Whole Thread \| Raw Message \| Download mbox \| Resend email
Thread:
Lists:	pgsql-hackers

On Tue, Sep 29, 2015 at 11:50:37PM +0200, Andres Freund wrote:
> On 2015-09-29 14:38:11 -0700, Josh Elsasser wrote:
> > I've put my changes up as a series of relatively small commits on this
> > branch of a github fork:
> >
> > https://github.com/jre/postgres/commits/single-tar
> >
> > Comments and suggestions are welcome.
>
> Please post them to the list, we want patches to be in our archives.

Sure, let's see if I can figure out git send-email

In response to

Re: Add pg_basebackup single tar output format at 2015-09-29 21:50:37 from Andres Freund

Responses

[PATCH 1/6] Add support for longer filenames in tar headers (up to 254 bytes). at 2015-09-29 22:16:23 from Joshua Elsasser
[PATCH 2/6] pg_basebackup: factor out tar open/close code for reusability. at 2015-09-29 22:16:24 from Joshua Elsasser
[PATCH 3/6] pg_basebackup: factor out code to add a recovery.conf file to the tar file. at 2015-09-29 22:16:25 from Joshua Elsasser
[PATCH 4/6] pg_basebackup: don't lose a zero-length file at the end of a tablespace. at 2015-09-29 22:16:26 from Joshua Elsasser
[PATCH 5/6] pg_basebackup: allow GetConnection() to make non-replication connections. at 2015-09-29 22:16:27 from Joshua Elsasser
[PATCH 6/6] pg_basebackup: add a single-tar output format. at 2015-09-29 22:16:28 from Joshua Elsasser
Re: Add pg_basebackup single tar output format at 2015-09-30 00:11:36 from Michael Paquier

Browse pgsql-hackers by date

	From	Date	Subject
Next Message	Joshua Elsasser	2015-09-29 22:16:23	[PATCH 1/6] Add support for longer filenames in tar headers (up to 254 bytes).
Previous Message	Stephen Frost	2015-09-29 22:15:22	Re: unclear about row-level security USING vs. CHECK