| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Greg Smith <greg(at)2ndquadrant(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: pgbench --unlogged-tables |
| Date: | 2011-07-25 13:23:01 |
| Message-ID: | CA+Tgmob54uZNwQ7ZJ5aPmsGjfPfhRY93Nk4VuOrX1p0j2Hpb9A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Jul 22, 2011 at 5:15 PM, Greg Smith <greg(at)2ndquadrant(dot)com> wrote:
> That looks straightforward enough.
OK, committed.
> The other thing I keep realizing would
> be useful recently is to allow specifying a different tablespace to switch
> to when creating all of the indexes. The old "data here, indexes on faster
> storage here" trick was already popular in some environments. But it's
> becoming a really big win for environments that put indexes on SSD, and
> being able to simulate that easily with pgbench would be nice.
Hearing no objections, I did this, too.
At some point, we also need to sort out the scale factor limit issues,
so you can make these things bigger.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tim | 2011-07-25 13:37:07 | Re: vacuumlo patch |
| Previous Message | Florian Pflug | 2011-07-25 12:48:16 | Re: Access to current database from C-language function |