From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | gmb <gmbouwer(at)gmail(dot)com> |
Cc: | postgres list <pgsql-sql(at)postgresql(dot)org> |
Subject: | Re: High memory usage / performance issue ( temp tables ? ) |
Date: | 2014-08-17 19:55:49 |
Message-ID: | CAFj8pRB44Hq8kdiwfQZRJVNLGz1Q2NAd_7RLrLJyi9Xgy3pwoA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
Hi
2014-08-17 21:47 GMT+02:00 gmb <gmbouwer(at)gmail(dot)com>:
> Something else I intended to ask in the original post, but forgot:
>
> What effect , if any , will the autovacuum setting have in this type of
> scenario ?
> Will performance be improved by disabling this ?
>
no, when you use temporary tables intensively - you must vacuum pg_catalog
intensively - vaccum should be more aggressive and faster then a bloating
of system catalog.
Probably you should to do REINDEX some system indexes more often than is
usually.
Regards
Pavel
> I assume that a vacuum process will be required on at least the pg_catalog
> due to dropping of temp tables during the process.
>
> Regards
>
> gmb
>
>
>
> --
> View this message in context:
> http://postgresql.1045698.n5.nabble.com/High-memory-usage-performance-issue-temp-tables-tp5815108p5815126.html
> Sent from the PostgreSQL - sql mailing list archive at Nabble.com.
>
>
> --
> Sent via pgsql-sql mailing list (pgsql-sql(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-sql
>
From | Date | Subject | |
---|---|---|---|
Next Message | gmb | 2014-08-18 05:33:18 | Re: High memory usage / performance issue ( temp tables ? ) |
Previous Message | gmb | 2014-08-17 19:47:26 | Re: High memory usage / performance issue ( temp tables ? ) |