Re: partitioned table set and indexes - Mailing list pgsql-performance

From Kevin Grittner
Subject Re: partitioned table set and indexes
Date
Msg-id CACjxUsOPqqF7B083GxdFcz1LWd76stVSgRy_WMLKU6VmTZ0krw@mail.gmail.com
Whole thread Raw
In response to partitioned table set and indexes  (Rick Otten <rottenwindfish@gmail.com>)
List pgsql-performance
On Fri, Dec 11, 2015 at 1:01 PM, Rick Otten <rottenwindfish@gmail.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


pgsql-performance by date:

Previous
From: Rick Otten
Date:
Subject: Re: partitioned table set and indexes
Next
From: Andreas Kretschmer
Date:
Subject: Re: partitioned table set and indexes