Re: Catalog views failed to show partitioned table information.

From: Suraj Kharage <suraj(dot)kharage(at)enterprisedb(dot)com>
To: michael(at)paquier(dot)xyz
Cc: Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Catalog views failed to show partitioned table information.
Date: 2018-12-18 09:57:11
Message-ID: CAF1DzPUMEhG-tXo7J5O1hjdcF256dzOt45mujtheFmJm-m4O6A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Thank you for review and commit.

On Tue, Dec 18, 2018 at 1:12 PM Michael Paquier <michael(at)paquier(dot)xyz> wrote:

> On Mon, Dec 17, 2018 at 11:01:59AM +0900, Michael Paquier wrote:
> > On Mon, Dec 17, 2018 at 10:22:28AM +0900, Amit Langote wrote:
> >> On 2018/12/15 8:00, Michael Paquier wrote:
> >>> I tend to agree with your comment here. pg_tables lists partitioned
> >>> tables, but pg_indexes is forgotting about partitioned indexes. So
> this
> >>> is a good thing to add.
> >>
> >> +1
> >
> > I'll go commit something close to what Suraj is proposing if there are
> > no objections from others. At least we agree on that part ;)
>
> And this part is done.
> --
> Michael
>

--
--

Thanks & Regards,
Suraj kharage,
EnterpriseDB Corporation,
The Postgres Database Company.

*Are you updated: Latest version of EnterpriseDB Postgres Advanced Server
are 10.6.13, 9.6.11.18, 9.5.15.21, 9.4.19.28*

To reach Support Call:
US +1-732-331-1320 or 1-800-235-5891
UK +44-2033 7198 20 - BRAZIL+55-2129 5813 71 -
INDIA+91-20-66449612 Australia: +61 26145 2339.

Website: www.enterprisedb.com
EnterpriseDB Blog : http://blogs.enterprisedb.com
Follow us on Twitter : http://www.twitter.com/enterprisedb

PRIVACY & CONFIDENTIALITY NOTICE

This e-mail message (and any attachment) is intended for the use of the
individual or entity to whom it is addressed. This message contains
information from EnterpriseDB Corporation that may be privileged,
confidential, or exempt from disclosure under applicable law. If you are
not the intended recipient or authorized to receive this for the intended
recipient, any use, dissemination, distribution,retention, archiving, or
copying of this communication is strictly prohibited. If you have received
this e-mail in error, please notify the sender immediately by reply e-mail
and delete this message.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavel Stehule 2018-12-18 10:11:47 Re: psql exit status with multiple -c or -f
Previous Message Kyotaro HORIGUCHI 2018-12-18 09:48:25 "repliation" as database name