Services
24×7×365 Technical Support
Migration to PostgreSQL
High Availability Deployment
Database Audit
Remote DBA for PostgreSQL
Products
Postgres Pro Enterprise
Postgres Pro Standard
Cloud Solutions
Postgres Extensions
Resources
Blog
Documentation
Webinars
Videos
Presentations
Community
Events
Training Courses
Books
Demo Database
Mailing List Archives
About
Leadership team
Partners
Customers
In the News
Press Releases
Press Info
Services
24×7×365 Technical Support
Migration to PostgreSQL
High Availability Deployment
Database Audit
Remote DBA for PostgreSQL
Products
Postgres Pro Enterprise
Postgres Pro Standard
Cloud Solutions
Postgres Extensions
Resources
Blog
Documentation
Webinars
Videos
Presentations
Community
Events
Training Courses
Books
Demo Database
Mailing List Archives
About
Leadership team
Partners
Customers
In the News
Press Releases
Press Info
Facebook
Downloads
Home
>
mailing lists
WARNING : pgstat wait timeout - stats_temp_directory - postgres 9.1 - Mailing list pgsql-hackers
From
Mathieu Guerin
Subject
WARNING : pgstat wait timeout - stats_temp_directory - postgres 9.1
Date
May 23, 2013
13:06:44
Msg-id
CAFssqjM7Fbop2QdQ-kyNn50C5oGKvV1Z0ayUisDGQdh5G9q3Cw@mail.gmail.com
Whole thread
Raw
Responses
Re: WARNING : pgstat wait timeout - stats_temp_directory - postgres 9.1
List
pgsql-hackers
Tree view
Hello,
I am facing a problem with pgstat as my subject says. I known, some topics are open about that, but I would like to go deeper.
Some person told that the better way to don't have this message anymore is to configure pgstat.stat to be loaded in the RAM with a tmpfs mount point.
What are the consequences ? Because this file will be remove if the server reboot.
If we change the parameter
stats_temp_directory
is it necessary to reboot the server ?
When I lauch a SHOW ALL; command, the parameter
stats_temp_director
is not here.
For information, my pgstat.stat file is up to 1,3MB.
Thank you for your help.
Math
pgsql-hackers
by date:
Previous
From:
Atri Sharma
Date:
23 May 2013, 13:04:57
Subject:
Time limit for a process to hold Content lock in Buffer Cache
Next
From:
Amit Kapila
Date:
23 May 2013, 13:58:25
Subject:
Re: Time limit for a process to hold Content lock in Buffer Cache
Есть вопросы? Напишите нам!
Соглашаюсь с условиями обработки персональных данных
I confirm that I have read and accepted PostgresPro’s
Privacy Policy
.
I agree to get Postgres Pro discount offers and other marketing communications.
✖
×
×
Everywhere
Documentation
Mailing list
List:
all lists
pgsql-general
pgsql-hackers
buildfarm-members
pgadmin-hackers
pgadmin-support
pgsql-admin
pgsql-advocacy
pgsql-announce
pgsql-benchmarks
pgsql-bugs
pgsql-chat
pgsql-cluster-hackers
pgsql-committers
pgsql-cygwin
pgsql-docs
pgsql-hackers-pitr
pgsql-hackers-win32
pgsql-interfaces
pgsql-jdbc
pgsql-jobs
pgsql-novice
pgsql-odbc
pgsql-patches
pgsql-performance
pgsql-php
pgsql-pkg-debian
pgsql-pkg-yum
pgsql-ports
pgsql-rrreviewers
pgsql-ru-general
pgsql-sql
pgsql-students
pgsql-testers
pgsql-translators
pgsql-www
psycopg
Period
anytime
within last day
within last week
within last month
within last 6 months
within last year
Sort by
date
reverse date
rank
Services
24×7×365 Technical Support
Migration to PostgreSQL
High Availability Deployment
Database Audit
Remote DBA for PostgreSQL
Products
Postgres Pro Enterprise
Postgres Pro Standard
Cloud Solutions
Postgres Extensions
Resources
Blog
Documentation
Webinars
Videos
Presentations
Community
Events
Training Courses
Books
Demo Database
Mailing List Archives
About
Leadership team
Partners
Customers
In the News
Press Releases
Press Info
By continuing to browse this website, you agree to the use of cookies. Go to
Privacy Policy
.
I accept cookies