On Tue, Sep 4, 2012 at 12:11:53PM -0500, Kevin Grittner wrote: > Bruce Momjian <br...@momjian.us> wrote: > > On Mon, Apr 9, 2012 at 02:07:43PM -0500, Kevin Grittner wrote: > >> Bruce Momjian <br...@momjian.us> wrote: > >>> On Mon, Apr 09, 2012 at 03:37:09PM -0300, Alvaro Herrera wrote: > >>> > >>>> (Another related tool is clearxlogtail which zeroes areas from > >>>> WAL files when they are empty because of an early switch due to > >>>> archive timeout). > >>> > >>> Should we document that? > >> > >> Our shop has been using that since before pglesslog existed, and > >> it has continued to work across many major releases with no > >> change to source code because it doesn't get down to the level of > >> looking at the xlog records themselves, just the segment and > >> page-level structures. I should probably put packaging that up > >> as a proper extension and posting it to PGXN as another thing on > >> the list of things I'll do when I stumble over that pot of round > >> tuits at the end of the rainbow. Right now the source is on > >> pgfoundry. If anybody wants to do anything with it before I find > >> time, feel free. > > > > I was going to add a mention of this to our docs, but it seems > > there are no released files for the project: > > There is a single 175 line C source file to generate a stand-alone > executable filter. The source has not needed any changes since it > was finished over 4 years ago. Besides that C file, there is only a > make file. I wasn't sure what form of packaging would be easier > than just checking out the source from the SCM. > > What do you think would be the right thing to do with it at this > point?
Well, there should probably be a tar files with a README. What about adding this to /contrib? -- Bruce Momjian <br...@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + It's impossible for everything to be true. + -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs