Re: Performance issue on temporary relations - Mailing list pgsql-hackers

From 章晨曦
Subject Re: Performance issue on temporary relations
Date
Msg-id tencent_3B2E5A5E6CCB7900226AB9B5@qq.com
Whole thread Raw
In response to Re: Performance issue on temporary relations  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
> BTW, it appears to me that doing it this way is O(N^2) in the number
> of active temp tables.  So it's not hard to believe that the patch
> as-presented would actually be a fairly serious performance drag for
> some use cases with lots of temp tables.  There are certainly ways
> we could do better than that (hash table, bloom filter, etc) but
> there would be even more engineering effort needed.

Yes, you're right. I also consider using like hash table to do more better and try
to merge the in_use list and on_commits list into one hashtable. But, as just you
said, it needs much more effort. Thanks any way.

Regards,
Jet

Halo Tech (www.halodbtech.com)
openHalo (www.openhalo.org)

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: VM corruption on standby
Next
From: Nathan Bossart
Date:
Subject: Re: Proper object locking for GRANT/REVOKE