On Fri, Oct 1, 2010 at 11:13, Fujii Masao <masao.fu...@gmail.com> wrote: > On Wed, Sep 29, 2010 at 5:47 PM, Magnus Hagander <mag...@hagander.net> wrote: >> It's actually intentional. If we create a file at first, there is no >> way to figure out exactly how far through a partial segment we are >> without parsing the details of the log. This is useful both for the >> admin (who can look at the directory and watch the file grow) and the >> tool itself (to know when the .save file can be rotated away, when >> recovering from a partial segment receive). >> >> My idea was to just have the admin pad the file when it's time to do >> the restore. I could perhaps even add an option to the tool to do it - >> the idea being it's a manual step still. >> >> Do you have another suggestion for how to provide those two things? > > My idea is to implement something like xlogdump in contrib and use it > for those two things. Though it's harder to implement that than to do > padding tool.
Yes, much harder. I prefer keeping the tool simple when possible ;) Doesn't mean we couldn't do both, i guess. > BTW, implementing something like xlogdump is already in TODO list: Yes, obviously such a tool would be very useful independent of the streaming thing. -- Magnus Hagander Me: http://www.hagander.net/ Work: http://www.redpill-linpro.com/ -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
