Bug#776948: [Pkg-postgresql-public] Bug#776948: RM: pgtune -- ROM; upstream dead, and bad advise to be used today

2015-02-19 Thread Christoph Berg
Re: Stuart Bishop 2015-02-04 CADmi=6nfza2a1eacgfcptf_zgupct-ju6lec-r3enuf8agc...@mail.gmail.com I don't think it's possible to get the necessary amount of changes into testing. What we could probably do is to just remove it from testing, and keep it in unstable for later updating.

Bug#776948: [Pkg-postgresql-public] Bug#776948: RM: pgtune -- ROM; upstream dead, and bad advise to be used today

2015-02-04 Thread Christoph Berg
Re: Scott Kitterman 2015-02-04 2026939.ppIJUsApvY@scott-latitude-e6320 pgtune hasn't seen a new upstream release since about the medieval ages, and the last git commit isn't very current either. The postgresql.conf it produces is worse than the defaults in some aspects, so people are

Bug#776948: [Pkg-postgresql-public] Bug#776948: RM: pgtune -- ROM; upstream dead, and bad advise to be used today

2015-02-04 Thread Stuart Bishop
On 4 February 2015 at 16:43, Christoph Berg christoph.b...@credativ.de wrote: Re: Scott Kitterman 2015-02-04 2026939.ppIJUsApvY@scott-latitude-e6320 pgtune hasn't seen a new upstream release since about the medieval ages, and the last git commit isn't very current either. The

Bug#776948: [Pkg-postgresql-public] Bug#776948: RM: pgtune -- ROM; upstream dead, and bad advise to be used today

2015-02-03 Thread Scott Kitterman
On Wednesday, February 04, 2015 12:33:02 Stuart Bishop wrote: On 3 February 2015 at 21:01, Christoph Berg christoph.b...@credativ.de wrote: Package: ftp.debian.org Severity: normal Hi, pgtune hasn't seen a new upstream release since about the medieval ages, and the last git

Bug#776948: [Pkg-postgresql-public] Bug#776948: RM: pgtune -- ROM; upstream dead, and bad advise to be used today

2015-02-03 Thread Stuart Bishop
On 3 February 2015 at 21:01, Christoph Berg christoph.b...@credativ.de wrote: Package: ftp.debian.org Severity: normal Hi, pgtune hasn't seen a new upstream release since about the medieval ages, and the last git commit isn't very current either. The postgresql.conf it produces is worse