Postgres Pro
Downloads
Home   >   mailing lists

Re: [HACKERS] Declarative partitioning - another take - Mailing list pgsql-hackers

From Robert Haas
Subject Re: [HACKERS] Declarative partitioning - another take
Date
Msg-id CA+TgmobqYiNsP-48eQp0Wjc12zHWa6Xo5J6uH94zqty98qFnnw@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] Declarative partitioning - another take  (Ildar Musin <i.musin@postgrespro.ru>)
Responses Re: [HACKERS] Declarative partitioning - another take  (Ildar Musin <i.musin@postgrespro.ru>)
List pgsql-hackers
Tree view 
On Tue, Dec 13, 2016 at 12:22 PM, Ildar Musin <i.musin@postgrespro.ru> wrote:
> We've noticed that PartitionDispatch object is built on every INSERT query
> and that it could create unnecessary overhead. Wouldn't it be better to keep
> it in relcache?

You might be able to cache some of that data in the relcache, but List
*keystate is pointing to query-lifespan data, so you can't cache that.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: [HACKERS] Hash Indexes
Next
From: Tom Lane
Date:
Subject: Re: [HACKERS] jsonb problematic operators