David Rowley wrote:
> On 6 December 2017 at 04:29, Robert Haas <robertmhaas@gmail.com> wrote:
> > On Mon, Dec 4, 2017 at 6:57 PM, David Rowley
> >> I proposed that this worked a different way in [1]. I think the way I
> >> mention is cleaner as it means there's no extra reason for a
> >> partitioned index to be indisvalid=false than there is for any other
> >> normal index.
> >
> > How does that proposal keep pg_dump from latching onto the wrong
> > index, if there's more than one index on the same columns?
>
> I'm not hugely concerned about that. It's not a new problem and it's
> not a problem that I recall seeing anyone complain about, at least not
> to the extent that we've ever bothered to fix it.
Another reason to do things the proposed way is to let parallel restore
create the indexes in parallel. If we just have a single CREATE INDEX
that cascades to the partitions, that can be run by a single backend
only, which is a loser.
(There's also the fact that you'd lose any COMMENTs etc).
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
