| From: | Kevin Grittner <kgrittn(at)gmail(dot)com> |
|---|---|
| To: | Rick Otten <rottenwindfish(at)gmail(dot)com> |
| Cc: | "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: partitioned table set and indexes |
| Date: | 2015-12-11 21:27:10 |
| Message-ID: | CACjxUsOPqqF7B083GxdFcz1LWd76stVSgRy_WMLKU6VmTZ0krw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Fri, Dec 11, 2015 at 1:01 PM, Rick Otten <rottenwindfish(at)gmail(dot)com> wrote:
> The first thing I noticed, when creating indexes on the 20 or so partitions,
> was that if I create them too fast they don't all succeed. I have to do a
> few at a time, let them breathe for a few seconds, and then do a few more.
> I had been simply generating all of the create index commands in a text
> editor, and then cutting and pasting the lot of them into psql all at once
I have seen problems with OS "paste" functionality dropping chunks of
pasted text if it was too big.
> or running them by using psql '-f'.
... but I would be surprised if that happened when reading from a file.
--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andreas Kretschmer | 2015-12-11 21:44:05 | Re: partitioned table set and indexes |
| Previous Message | Rick Otten | 2015-12-11 20:40:30 | Re: partitioned table set and indexes |