On Sat, Nov 7, 2009 at 9:58 PM, Aris Samad-Yahaya wrote:
> We vacuum analyze nightly, and vacuum normally ad-hoc (but we're going to
> schedule this weekly moving forward).
>
> Interesting pointer about system catalog bloat. I tried to vacuum full the
> system catalog tables (pg_*), and the perfor
We vacuum analyze nightly, and vacuum normally ad-hoc (but we're going to
schedule this weekly moving forward).
Interesting pointer about system catalog bloat. I tried to vacuum full the
system catalog tables (pg_*), and the performance for creating a single
table manually improved dramatically (b
Hi Craig,
Yes we do put the creation of the 300 tables into a single transaction. The
difference between putting them in a single transaction and individual
transactions is about 30 seconds over the 3 minutes.
As for the creation of 300 individual tables for an account... yes we were
trying to th
On 8/11/2009 11:15 AM, Aris Samad-Yahaya wrote:
> It used to take about 15 seconds to create those 300 tables in a new
> schema (when there were only a few schemas, say about 50). It now takes
> about 3 minutes (and now we have about 200 schemas, with more data but
> not hugely so).
200 schemas,
"Aris Samad-Yahaya" writes:
> I'm facing a problem where running a CREATE TABLE has slowed down
> significantly over time.
System catalog bloat maybe? What are your vacuuming practices?
regards, tom lane
--
Sent via pgsql-performance mailing list (pgsql-performance@pos
I'm facing a problem where running a CREATE TABLE has slowed down
significantly over time.
This is problematic because my application needs to routinely create a new
schema and create 300 tables in each new schema. In total it takes about 3
minutes, which may not seem like a big deal, but this
