Re: [PERFORM] Size of Temporary tablespace is increasing very much inpostgresql 9.1. - Mailing list pgsql-performance

From Dinesh Chandra 12108
Subject Re: [PERFORM] Size of Temporary tablespace is increasing very much inpostgresql 9.1.
Date
Msg-id 62944b5c5ba94d10a76639956c1c548f@cyient.com
Whole thread Raw
In response to Re: [PERFORM] Size of Temporary tablespace is increasing very much inpostgresql 9.1.  (Mark Kirkwood <mark.kirkwood@catalyst.net.nz>)
List pgsql-performance
Dear Mark,

Thanks for your valuable comment.
Now problem is resolved.

Regards,
Dinesh Chandra
|Database administrator (Oracle/PostgreSQL)| Cyient Ltd. Noida.
------------------------------------------------------------------
Mobile: +91-9953975849 | Ext 1078 |dinesh.chandra@cyient.com
Plot No. 7, NSEZ, Phase-II ,Noida-Dadri Road, Noida - 201 305,India.

-----Original Message-----
From: Mark Kirkwood [mailto:mark.kirkwood@catalyst.net.nz]
Sent: 17 December, 2016 7:28 AM
To: Dinesh Chandra 12108 <Dinesh.Chandra@cyient.com>; pgsql-performance@postgresql.org
Subject: Re: [PERFORM] Size of Temporary tablespace is increasing very much in postgresql 9.1.

On 15/12/16 23:28, Dinesh Chandra 12108 wrote:

> Dear expert,
>
> In postgreSQL-9.1,the size of *pgsql_tmp* inside tablespace (Temp
> tablespace) is increased by 544G in one day.
>
> However, the DBsize is as usual but tablespace size is getting increased.
>
> Could you please suggest why it is happening ?
>
>

That is due to queries doing sorts or (hash) joins. You can log which queries are doing this with the log_temp_files
parameter.

Now it might be that this is just normal/expected (e.g complex data warehouse style workload), but it could also be
manysmall queries that might benefit from some additional indexes (logging the queries will help you decide what if
anythingneeds to be done). 

regards

Mark

________________________________

DISCLAIMER:

This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged
information.Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended
recipient,please contact the sender by reply email and destroy all copies of the original message. Check all
attachmentsfor viruses before opening them. All views or opinions presented in this e-mail are those of the author and
maynot reflect the opinion of Cyient or those of our affiliates. 


pgsql-performance by date:

Previous
From: Tom Lane
Date:
Subject: Re: [PERFORM] bad performance
Next
From: Dinesh Chandra 12108
Date:
Subject: [PERFORM] How to vacuum entire database excluding some tables in PostgreSQL9.1.