From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Maksim Milyutin <m(dot)milyutin(at)postgrespro(dot)ru> |
Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Proposal: Local indexes for partitioned table |
Date: | 2017-04-10 11:20:49 |
Message-ID: | CA+TgmoY5UOUnW=McwT7xUB_2W5dAkvOg5kD20Spx5gF-Ad47cA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Apr 4, 2017 at 12:10 PM, Maksim Milyutin
<m(dot)milyutin(at)postgrespro(dot)ru> wrote:
> 1. I have added a new relkind for local indexes named RELKIND_LOCAL_INDEX
> (literal 'l').
Seems like it should maybe be RELKIND_PARTITIONED_INDEX. There's
nothing particularly "local" about it. I suppose what you're going
for is that it's not global, but in a way it *is* global to the
partitioning hierarchy. That's the point. It's just that it's
partitioned.
> Perhaps, it's not good way to use pg_depend to determine the relationship
> between parent and child indexes because the kind of this relationship is
> not defined. I could propose to add into pg_index table specific field of
> 'oidvector' type that specify oids of dependent indexes for the current
> local index.
I agree with Greg's comment on this point.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Maksim Milyutin | 2017-04-10 11:32:11 | Re: Proposal: Local indexes for partitioned table |
Previous Message | Greg Stark | 2017-04-10 11:07:21 | Re: Variable substitution in psql backtick expansion |