Re: [RFC] What should we do for reliable WAL archiving?
От | MauMau |
---|---|
Тема | Re: [RFC] What should we do for reliable WAL archiving? |
Дата | |
Msg-id | 94F13A624B5F411D8792858B76294015@maumau обсуждение исходный текст |
Ответ на | Re: [RFC] What should we do for reliable WAL archiving? (Michael Paquier <michael.paquier@gmail.com>) |
Список | pgsql-hackers |
From: "Michael Paquier" <michael.paquier@gmail.com> > On Fri, Mar 21, 2014 at 8:54 PM, MauMau <maumau307@gmail.com> wrote: >> * Create pg_copy in C so that it can be used on Windows as well as on >> UNIX/Linux. It just copies one file. Its source code is located in >> src/bin/pg_copy/. Please recommend a better name if you have one in >> mind. > I'd rather see that as a part of contrib/ if possible. Is there any > portion of the code you have in mind that makes mandatory putting it > in src/bin? Archiving transaction logs reliably is a basic responsibility of DBMS, so I think it should be treated as part of the core. It is not a desirable feature but actually a mandatory one to persist transaction logs. Even if it were a "better to have" feature, it can be put in the core like pg_basebackup and pg_isready, which are not mandatory tools. >> * Should I complete the work before 9.4 beta so that it will be available >> starting with 9.4? I think so because it is a basic capability to >> archive >> transaction logs safely (although the time may not allow me to do this). > Pursing efforts on a utility like that is worth the shot IMO (I would > use it for sure if it has reliable cross-platform support to unify > sets of replication scripts), but including it in 9.4 is out of scope. > A saner target would be the 1st commit fest of 9.5. OK, I don't mind if it should be targeted at 9.4 or 9.5. If someone wants it for 9.4, I try to hurry. Regards MauMau
В списке pgsql-hackers по дате отправления: