Re: pg_dump getBlobs query broken for 7.3 servers

Поиск
Список
Период
Сортировка
От Alvaro Herrera
Тема Re: pg_dump getBlobs query broken for 7.3 servers
Дата
Msg-id 20161007173100.GA780434@alvherre.pgsql
обсуждение исходный текст
Ответ на Re: pg_dump getBlobs query broken for 7.3 servers  (Stephen Frost <sfrost@snowman.net>)
Ответы Re: pg_dump getBlobs query broken for 7.3 servers  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: pg_dump getBlobs query broken for 7.3 servers  (Stephen Frost <sfrost@snowman.net>)
Список pgsql-hackers
Stephen Frost wrote:
> * Alvaro Herrera (alvherre@2ndquadrant.com) wrote:
> > Stephen Frost wrote:
> > 
> > > What would be really nice would be code coverage information for the
> > > back-branches also, as that would allow us to figure out what we're
> > > missing coverage for.  I realize that we don't like adding new things to
> > > back-branches as those changes could impact packagers, but that might
> > > not impact them since that only runs when you run 'make coverage'.
> > 
> > Hmm?  9.1 already has "make coverage", so there's nothing to backpatch.
> > Do you mean to backpatch that infrastructure even further back than
> > that?
> 
> I wasn't sure how far back it went, but if it's only to 9.1, then yes,
> farther than that.  Specifically, to as far back as we wish to provide
> support for pg_dump, assuming it's reasonable to do so.

I said 9.1 because that's the oldest we support, but it was added in
8.4.

Do you really want to go back to applying patches back to 7.0?  That's
brave.

> > Or perhaps you are saying that coverage.pg.org should report results for
> > each branch separately?  We could do that ...
> 
> This would certainly be nice to have, but the first is more important.
> coverage.pg.org is nice to tell people "hey, here's where you can look
> to find what we aren't covering", but when you're actually hacking on
> code, you really want a much faster turn-around

True.  We could actually update things in coverage.postgresql.org much
faster, actually.  Right now it's twice a day, but if we enlarge the
machine I'm sure we can do better (yes, we can do that pretty easily).
Also, to make it faster, we could install ccache 3.10 in that machine,
although that would be against our regular pginfra policy.

At some point I thought about providing reports for each day, so that we
can see how it has improved over time, but that may be too much :-)

> and you'd like that pre-commit too.

Yeah, that's a good point.

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Stephen Frost
Дата:
Сообщение: Re: pg_dump getBlobs query broken for 7.3 servers
Следующее
От: Tom Lane
Дата:
Сообщение: Re: pg_dump getBlobs query broken for 7.3 servers