Re: some pg_dump query code simplification

From: Stephen Frost <sfrost(at)snowman(dot)net>
To: Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: some pg_dump query code simplification
Date: 2018-08-30 23:25:07
Message-ID: 20180830232507.GV3326@tamriel.snowman.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Greetings,

* Andrew Dunstan (andrew(dot)dunstan(at)2ndquadrant(dot)com) wrote:
> On 08/28/2018 06:05 PM, Tom Lane wrote:
> >Dunno about the idea of running the pg_dump TAP tests against back
> >branches. I find that code sufficiently unreadable that maintaining
> >several more copies of it doesn't sound like fun at all.
>
> Agreed. The code could do with a lot of comments. I recently looked at
> adding something to it and decided I had more pressing things to do.

I'm happy to add more comments to it.. There's a pretty good block that
tries to describe how the tests work above where the tests are actually
defined. What would help? Should I include an example in that code
block? Or are you looking for more comments in the actual test
definitions about what they're covering or why they're included? Or are
you interested in comments about the actual code down at the bottom
which runs the tests..?

Thanks!

Stephen

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2018-08-30 23:37:37 Re: pg_verify_checksums and -fno-strict-aliasing
Previous Message Stephen Frost 2018-08-30 23:23:20 Re: some pg_dump query code simplification