On 9/07/2011 8:26 PM, pasman pasmański wrote:
Reality is crude, seems than this idea is not as good as i think :(
Thanks for answer.
No worries.
For what it's worth, PostgreSQL caches recently used tuples in shared
memory anyway. The OS caches disk data in RAM too. So if the foreign key
is
Reality is crude, seems than this idea is not as good as i think :(
Thanks for answer.
2011/7/9, Craig Ringer :
> On 9/07/2011 3:06 PM, pasman pasmański wrote:
>> Hi.
>>
>> Today i have an idea for increase performance of foreign keys. After
>> search parent record, store ctid in shared memory.
On 9/07/2011 3:06 PM, pasman pasmański wrote:
Hi.
Today i have an idea for increase performance of foreign keys. After
search parent record, store ctid in shared memory. Subsequent searches
look first to the record at stored ctid, and when it is deleted do
regular search using index.
How many
Hi.
Today i have an idea for increase performance of foreign keys. After
search parent record, store ctid in shared memory. Subsequent searches
look first to the record at stored ctid, and when it is deleted do
regular search using index.
Pro: faster searching for common keys when parent table is
