Re: Bug when dumping "empty" operator classes

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org>, Stephen Frost <sfrost(at)snowman(dot)net>, Daniel Gustafsson <daniel(at)yesql(dot)se>
Subject: Re: Bug when dumping "empty" operator classes
Date: 2017-05-29 21:01:12
Message-ID: CAB7nPqQ2Y4wQOtQzvb-9WYnPu1CzT=2WkVXkSEuN8AKqe3f90A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, May 26, 2017 at 8:14 AM, Daniel Gustafsson <daniel(at)yesql(dot)se> wrote:
>> On 26 May 2017, at 17:08, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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.
>
> Thanks!

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?
--
Michael

Attachment Content-Type Size
pgdump-tap-empty-opclass.patch application/octet-stream 1.8 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Mark Kirkwood 2017-05-29 21:06:48 Re: logical replication - still unstable after all these months
Previous Message Michael Paquier 2017-05-29 20:49:05 Re: [PATCH] Fixed malformed error message on malformed SCRAM message.