Re: Should TIDs be typbyval = FLOAT8PASSBYVAL to speed up CREATE INDEX CONCURRENTLY? - Mailing list pgsql-hackers

From Jeff Janes
Subject Re: Should TIDs be typbyval = FLOAT8PASSBYVAL to speed up CREATE INDEX CONCURRENTLY?
Date
Msg-id CAMkU=1zSFX81gd0qXDcaSO2E4=86W00PDNkOoe0Wcf0KquUuyg@mail.gmail.com
Whole thread Raw
In response to Re: Should TIDs be typbyval = FLOAT8PASSBYVAL to speed up CREATE INDEX CONCURRENTLY?  (Corey Huinker <corey.huinker@gmail.com>)
List pgsql-hackers
On Sat, Dec 12, 2015 at 9:48 AM, Corey Huinker <corey.huinker@gmail.com> wrote:
>
>
> What, if any, other load should be placed on the underlying table during the
> test?
>
> I ask because CIC statements that run in seconds on our staging machine can
> take many hours on our production machine, when most of the access is just
> reads, though those reads may have been part of a larger transaction that
> did updates elsewhere.

That sounds like the CIC is just blocked waiting for long-lived
transactions to go away.  There isn't much that changes to the sorting
algorithm can do about that.

Cheers,

Jeff



pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: PATCH: track last known XLOG segment in control file
Next
From: Tom Lane
Date:
Subject: Re: Using a single standalone-backend run in initdb (was Re: Bootstrap DATA is a pita)