Re: pg_basebackup for streaming base backups
От | Magnus Hagander |
---|---|
Тема | Re: pg_basebackup for streaming base backups |
Дата | |
Msg-id | AANLkTinWyn6HwKt+XKSLnsauocWnOsMTvK+bMi0EDH1C@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: pg_basebackup for streaming base backups (Dimitri Fontaine <dimitri@2ndQuadrant.fr>) |
Ответы |
Re: pg_basebackup for streaming base backups
|
Список | pgsql-hackers |
On Sat, Jan 15, 2011 at 23:10, Dimitri Fontaine <dimitri@2ndquadrant.fr> wrote: >>> That should be -D --pgdata, for consistency with pg_dump. >> >> pg_dump doesn't have a -D. I assume you mean pg_ctl / initdb? > > Yes, sorry, been too fast. Ok. Updated patch that includes this change attached. I also changed the tar directory from -t to -T, for consistency. It also includes the change to take -h host, -U user, -w/-W for password -p port instead of a conninfo string. >> Another option, I think Heikki mentioned this on IM at some point, is >> to do something like name it <oid>-<name>.tar. That would give us best >> of both worlds? > > Well I'd think we know the pg_tablespace columns encoding, so the > problem might be the filesystem encodings, right? Well there's also the Do we really? That's one of the global catalogs that don't really have an encoding, isn't it? > option of creating <oid>.tar and have a symlink to it called <name>.tar > but that's pushing it. I don't think naming after OIDs is a good > service for users, but if that's all we can reasonably do… Yeah, symlink seems to be making things way too complex. <oid>-<name> seems is perhaps a reasonable compromise? > Will continue reviewing and post something more polished and > comprehensive next week — mainly wanted to see if you wanted to include > pg_ctl <command> in the patch already. Ok, thanks. -- Magnus Hagander Me: http://www.hagander.net/ Work: http://www.redpill-linpro.com/
Вложения
В списке pgsql-hackers по дате отправления: