| From: | Peter Geoghegan <pg(at)heroku(dot)com> |
|---|---|
| To: | Corey Huinker <corey(dot)huinker(at)gmail(dot)com> |
| Cc: | 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-11 22:35:04 |
| Message-ID: | CAM3SWZTXoKzsyUFab1Ft9XsfY7Y73gFH95dTaUqRZVzz_x2Gfg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Dec 11, 2015 at 2:26 PM, Corey Huinker <corey(dot)huinker(at)gmail(dot)com> wrote:
> Sure, the machine we called "ninefivealpha", which incidentally, failed to
> find a single bug in alpha2 thru beta2, is currently idle, and concurrent
> index creation times are a bugbear around these parts. Can somebody, either
> in this thread or privately, outline what sort of a test they'd like to see?
Any kind of CREATE INDEX CONCURRENTLY test, before and after.
I looked at a simple, random int4 column. That seems like a good case
to focus on, since there isn't too much other overhead. I think I
performed my test on an unlogged table, to make sure other overhead
was even further minimized.
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2015-12-11 22:40:11 | Re: Bootstrap DATA is a pita |
| Previous Message | Corey Huinker | 2015-12-11 22:26:41 | Re: Should TIDs be typbyval = FLOAT8PASSBYVAL to speed up CREATE INDEX CONCURRENTLY? |