Skip site navigation (1) Skip section navigation (2)

Re: Base Backup Streaming

From: Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr>
To: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
Cc: Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr>, Josh Berkus <josh(at)postgresql(dot)org>, Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>, Simon Riggs <simon(at)2ndQuadrant(dot)com>, greg(at)2ndQuadrant(dot)com, Hannu Krosing <hannu(at)2ndquadrant(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Base Backup Streaming
Date: 2011-01-02 17:53:51
Message-ID: m2r5cvry34.fsf@2ndQuadrant.fr (view raw or flat)
Thread:
Lists: pgsql-hackers
Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> writes:
> http://archives.postgresql.org/message-id/4C80D9B8.2020301@enterprisedb.com
>
> That just needs to be polished into shape, and documentation.

Wow, cool!  I don't know how but I've missed it.

> +1. Or maybe it would be better make it a separate binary, rather than part
> of pg_ctl.

Well the thinking was that nowadays we support initdb from pg_ctl, and
this is another kind of initdb, really.

> I linked above. Running queries requires connecting to a real database,
> which means that the user needs to have privileges to do that and you need
> to know the name of a valid database. Ideally this would all work through a
> replication connection. I think we should go with that from day one.

I didn't think about the "connecting to a real database" part of it,
versus using a dedicated REPLICATION connection/protocol, and to be
honest, I feared it was too much work.  Seeing that you already did it,
though, +1.

Regards,
-- 
Dimitri Fontaine
http://2ndQuadrant.fr     PostgreSQL : Expertise, Formation et Support

In response to

Responses

pgsql-hackers by date

Next:From: Kevin GrittnerDate: 2011-01-02 18:13:00
Subject: Re: management of large patches
Previous:From: Simon RiggsDate: 2011-01-02 17:43:02
Subject: Re: Sync Rep Design

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group