Re: [HACKERS] Bug when dumping "empty" operator classes - Mailing list pgsql-hackers

From Stephen Frost
Subject Re: [HACKERS] Bug when dumping "empty" operator classes
Date
Msg-id 20181208011142.GU3415@tamriel.snowman.net
Whole thread Raw
In response to Re: [HACKERS] Bug when dumping "empty" operator classes  (Michael Paquier <michael.paquier@gmail.com>)
Responses Re: [HACKERS] Bug when dumping "empty" operator classes  (Michael Paquier <michael@paquier.xyz>)
Re: [HACKERS] Bug when dumping "empty" operator classes  (Stephen Frost <sfrost@snowman.net>)
List pgsql-hackers
Greetings,

* Michael Paquier (michael.paquier@gmail.com) wrote:
> On Fri, May 26, 2017 at 8:14 AM, Daniel Gustafsson <daniel@yesql.se> wrote:
> >> On 26 May 2017, at 17:08, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> >> I'll commit and back-patch this without a test case.  Possibly Frost will
> >> be excited enough about it to add something to the pg_dump TAP tests,
> >> but those tests are too opaque for me to want to do so.
>
> For the TAP tests I think that you are looking for something like the
> attached. Stephen, perhaps you could consider including this test in
> the suite?

Another blast from the past.  I've updated this to the new pg_dump
test-suite system but otherwise it's basically the same test.

Barring concerns, I'll plan to push this later this weekend.

Thanks!

Stephen

Attachment

pgsql-hackers by date:

Previous
From: Alexander Korotkov
Date:
Subject: Re: Statement-level rollback
Next
From: Tatsuo Ishii
Date:
Subject: extended query protcol violation?