| From: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
|---|---|
| To: | Corey Huinker <corey(dot)huinker(at)gmail(dot)com> |
| Cc: | Peter Geoghegan <pg(at)heroku(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Should TIDs be typbyval = FLOAT8PASSBYVAL to speed up CREATE INDEX CONCURRENTLY? |
| Date: | 2015-12-13 05:33:13 |
| Message-ID: | CAMkU=1zSFX81gd0qXDcaSO2E4=86W00PDNkOoe0Wcf0KquUuyg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, Dec 12, 2015 at 9:48 AM, Corey Huinker <corey(dot)huinker(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2015-12-13 05:40:15 | Re: Using a single standalone-backend run in initdb (was Re: Bootstrap DATA is a pita) |
| Previous Message | Amit Kapila | 2015-12-13 05:24:04 | Re: PATCH: track last known XLOG segment in control file |