Re: Proposal: Local indexes for partitioned table

Tom Lane <tgl@sss.pgh.pa.us>

From: Tom Lane <tgl@sss.pgh.pa.us>

To: Alvaro Herrera <alvherre@alvh.no-ip.org>

Cc: Robert Haas <robertmhaas@gmail.com>, Pg Hackers <pgsql-hackers@postgresql.org>, Maksim Milyutin <milyutinma@gmail.com>, Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>

Date: 2017-11-03T19:09:04Z

Lists: pgsql-hackers

Alvaro Herrera <alvherre@alvh.no-ip.org> writes:
> Tom Lane wrote:
>> It might work to build the new key in a context that's initially a
>> child of CurrentMemoryContext, then reparent it to be a child of
>> CacheMemoryContext when done. 

> That's another way (than the PG_TRY block), but I think it's more
> complicated with no gain.

I disagree: PG_TRY blocks are pretty expensive.

			regards, tom lane

Commits

Local partitioned indexes
- 8b08f7d4820f 11.0 landed
Fix StoreCatalogInheritance1 to use 32bit inhseqno
- 1ef61ddce908 11.0 landed
- 9a215fb4b5ec 9.3.21 landed
- 8a71ee628854 9.6.7 landed
- 61f08c016322 10.2 landed
- 1284d18b5de9 9.4.16 landed
- 0d993709a773 9.5.11 landed
Get rid of copy_partition_key
- 8a0596cb656e 11.0 landed
Simplify index_[constraint_]create API
- a61f5ab98638 11.0 landed