Re: Patch: ResourceOwner optimization for tables with many partitions - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Patch: ResourceOwner optimization for tables with many partitions
Date
Msg-id 15276.1453743885@sss.pgh.pa.us
Whole thread Raw
In response to Re: Patch: ResourceOwner optimization for tables with many partitions  (Aleksander Alekseev <a.alekseev@postgrespro.ru>)
Responses Re: Patch: ResourceOwner optimization for tables with many partitions  (Aleksander Alekseev <a.alekseev@postgrespro.ru>)
List pgsql-hackers
Aleksander Alekseev <a.alekseev@postgrespro.ru> writes:
> I compared two implementations - "always use hashing" (step2a.path) and
> "use hashing only for large arrays" (step2b.path). Both patches give
> the same performance according to benchmark I described in a first
> message of this thread.

Um, that's not too surprising, because they're exactly the same patch?
        regards, tom lane



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: is there a deep unyielding reason to limit U&'' literals to ASCII?
Next
From: Andres Freund
Date:
Subject: Re: Set search_path + server-prepared statements = cached plan must not change result type