fantastic !
thanks.
greg
>
> From: Jaime Casanova
>To: Greg Williamson
>Cc: "pgsql-admin@postgresql.org"
>Sent: Wednesday, October 17, 2012 10:05 AM
>Subject: Re: [ADMIN] Database size stays constant but disk space keeps
>s
On Wed, Oct 3, 2012 at 4:53 PM, Greg Williamson wrote:
>
> Indeed -- stopping repmgr has lef to a continued accumulation of the dead but
> not gone file handles, but almost all are now owned by the application, with
> only a few held by WAL shipping and the like. So repmgr was just getting the
Gabriele --
- Original Message -
> From: Gabriele Bartolini
> To: Greg Williamson
> Cc: pgsql-admin@postgresql.org
> Sent: Wednesday, October 3, 2012 4:41 AM
> Subject: Re: [ADMIN] Database size stays constant but disk space keeps
> shrinking -- postgres 9.1
>
&
On Wed, Oct 3, 2012 at 6:41 AM, Gabriele Bartolini
wrote:
> Hi Greg,
>
>
> On Tue, 2 Oct 2012 15:02:23 -0700 (PDT), Greg Williamson
> wrote:
>
>> Other than abandoning repmgr I don't see a solution. I've posted this
>> to the repmgr discussion group but have had zero responses (and,
>> frankly, a
Hi Greg,
On Tue, 2 Oct 2012 15:02:23 -0700 (PDT), Greg Williamson
wrote:
Other than abandoning repmgr I don't see a solution. I've posted this
to the repmgr discussion group but have had zero responses (and,
frankly, am not holding my breath).
If you are 100% sure it is repmgr ... :)
I am
I've done some more testing and the problem seems to be repmgr itself.
A few details below...
- Original Message -
> From: Greg Williamson
> To: Tom Lane
> Cc: "pgsql-admin@postgresql.org"
> Sent: Thursday, September 27, 2012 7:23 PM
> Subject: R
Dinesh --
- Original Message -
> From: Dinesh Bhandary
> To: Greg Williamson
> Cc: "pgsql-admin@postgresql.org"
> Sent: Thursday, September 27, 2012 7:19 PM
> Subject: Re: [ADMIN] Database size stays constant but disk space keeps
> shrinking -- postgr
wrote:
>Steve (and others who replied):
>
>
>- Original Message -
>>From: Steve Crawford
>>To: Greg Williamson
>>Cc: "pgsql-admin@postgresql.org"
>>Sent: Thursday, September 27, 2012 3:48 PM
>>Subject: Re: [ADMIN] Database size stays constant
Greg Williamson writes:
>> I'll leave it to you and Tom to puzzle over the the postgres-related open
>> files. Meanwhile, I'm a bit curious about the other 800+ and whether they
>> are associated with scripts or processes that are connected to PostgreSQL.
> These all seem to be from two places
Steve --
- Original Message -
> From: Steve Crawford
> To: Greg Williamson
> Cc: "pgsql-admin@postgresql.org"
> Sent: Friday, September 28, 2012 8:59 AM
> Subject: Re: [ADMIN] Database size stays constant but disk space keeps
> shrinking -- postgres 9.1
We had a situation where external sort was creating a humungous temp
file and the space was reclaimed when the process was completed.
Thanks.
Dinesh
On 9/28/2012 8:59 AM, Steve Crawford wrote:
On 09/27/2012 07:01 PM, Greg Williamson wrote:
Steve (and others who replied):
...
The other is a
On 09/27/2012 07:01 PM, Greg Williamson wrote:
Steve (and others who replied):
...
The other is a slimmed-down version of our production database, which gets
recreated hourly by a shell script which pulls data from remote servers, does a
pg_dump of the resulting 3 gig database, and then drops
Tom --
- Original Message -
> From: Tom Lane
> To: Greg Williamson
> Cc: "pgsql-admin@postgresql.org"
> Sent: Thursday, September 27, 2012 7:55 PM
> Subject: Re: [ADMIN] Database size stays constant but disk space keeps
> shrinking -- postgres 9.1
Greg Williamson writes:
>>> postgres 2540 postgres 50u REG8,3 409600
>>> 93429 /var/lib/postgresql/9.1/main/base/2789200/11816 (deleted)
>>> postgres 2540 postgres 51u REG8,3 18112512
>>> 49694570 /var/lib/postgresql/9.1/main/base/278
Tom --
- Original Message -
> From: Tom Lane
> To: Greg Williamson
> Cc: "pgsql-admin@postgresql.org"
> Sent: Thursday, September 27, 2012 7:14 PM
> Subject: Re: [ADMIN] Database size stays constant but disk space keeps
> shrinking -- postgres 9.1
Greg Williamson writes:
>> Have you checked to see if there are any processes that have open handles to
>> deleted files (lsof -X | grep deleted).
> lsof -X | grep deleted | wc -l
> shows: 835 such files.
> A couple:
> postgres 2540 postgres 50u REG8,3 409600
Steve (and others who replied):
- Original Message -
> From: Steve Crawford
> To: Greg Williamson
> Cc: "pgsql-admin@postgresql.org"
> Sent: Thursday, September 27, 2012 3:48 PM
> Subject: Re: [ADMIN] Database size stays constant but disk space keeps
&g
You might also want to check to see if temp files are growing out of bounds.
Thanks.
Dinesh
On 9/27/2012 3:05 PM, Greg Williamson wrote:
Dear list,
I have a postgres database, 9.1.3, which shows a fairly constant amount of
space used by postgres, but total disk space kees shrinking.
If I resta
Hi Greg,
On Fri, Sep 28, 2012 at 8:05 AM, Greg Williamson wrote:
>
> I have a postgres database, 9.1.3, which shows a fairly constant amount of
> space used by postgres, but total disk space kees shrinking.
> If I restart postgres the space on my file system returns.
>
It sounds like (maybe?) Po
On 09/27/2012 03:05 PM, Greg Williamson wrote:
Dear list,
I have a postgres database, 9.1.3, which shows a fairly constant amount of
space used by postgres, but total disk space kees shrinking.
If I restart postgres the space on my file system returns.
This cluster is replicated to another; th
Dear list,
I have a postgres database, 9.1.3, which shows a fairly constant amount of
space used by postgres, but total disk space kees shrinking.
If I restart postgres the space on my file system returns.
This cluster is replicated to another; that custer does not show this problem.
There are
Rob Audenaerde writes:
> It gets stranger. I try this:
> select
> tablename
> , pg_relation_size(tablename)
> , pg_size_pretty(pg_relation_size(tablename) ) as relsize
> , pg_size_pretty(pg_total_relation_size(tablename) ) as disksize
> , pg_total_relation_size(tablename)
> from pg_tables whe
I check te database size like this:
select pg_size_pretty(pg_database_size('database'))
595 GB
>>> You should also check the space held in $PGDATA/base.
>> I did. It is only 320 MB.
>Bizarre. Try breaking the results down table-by-table to see if you can
>find where the discrepan
Rob Audenaerde writes:
>>> I check te database size like this:
>>> select pg_size_pretty(pg_database_size('database'))
>>> 595 GB
>> You should also check the space held in $PGDATA/base.
> I did. It is only 320 MB.
Bizarre. Try breaking the results down table-by-table to see if you can
find wh
>On Wed, 2011-09-14 at 04:03 -0700, Rob Audenaerde wrote:
>> I have a Postgresql 8.3 instance with tablespaces totalling on about 74G.
>> This is fine.
>>
>> But if I ask Postgresql how big my database is, I get a (unexpected) large
>> answer: 595 GB.
>>
>> This seems very strange. Disk I/O tests
On Wed, 2011-09-14 at 04:03 -0700, Rob Audenaerde wrote:
> I have a Postgresql 8.3 instance with tablespaces totalling on about 74G.
> This is fine.
>
> But if I ask Postgresql how big my database is, I get a (unexpected) large
> answer: 595 GB.
>
> This seems very strange. Disk I/O tests on th
Hi,
On Wed, 14 Sep 2011 04:03:45 -0700, Rob Audenaerde
wrote:
Is this corruption of the database? Or are there ways to 'fix' this
oddity?
Try VACUUM ANALYSE and repeat the operation.
Thanks,
Gabriele
--
Gabriele Bartolini - 2ndQuadrant Italia
PostgreSQL Training, Services and Support
ga
I have a Postgresql 8.3 instance with tablespaces totalling on about 74G. This
is fine.
But if I ask Postgresql how big my database is, I get a (unexpected) large
answer: 595 GB.
This seems very strange. Disk I/O tests on the system are in the 'normal'
range, but queries are slower than they u
Le 27/03/2010 14:00, Gnanakumar a écrit :
> [...]
> We're using PostgreSQL 8.2. Recently, in our production database, there was
> a severe performance impact.. Even though, we're regularly doing both:
>
> 1. VACUUM FULL ANALYZE once in a week during low-usage time and
>
> 2. ANALYZE eve
;
pgsql-performa...@postgresql.org
Subject: [ADMIN] Database size growing over time and leads to performance impact
Hi,
We're using PostgreSQL 8.2. Recently, in our production database, there was
a severe performance impact.. Even though, we're regularly doing both:
1. V
Hi,
We're using PostgreSQL 8.2. Recently, in our production database, there was
a severe performance impact.. Even though, we're regularly doing both:
1. VACUUM FULL ANALYZE once in a week during low-usage time and
2. ANALYZE everyday at low-usage time
Also, we noticed that the
On Thu, Jun 19, 2008 at 7:18 PM, Joshua D. Drake <[EMAIL PROTECTED]> wrote:
> Kunal Gupta wrote:
>>
>> Hi ,
>>
>> I have a question, I am suppose to create database with limited size. Is
>> there any way I can set limit to my database created in postgresql.
>
> Not reasonably no.
>
>> - Since in po
Kunal Gupta wrote:
Hi ,
I have a question, I am suppose to create database with limited size. Is
there any way I can set limit to my database created in postgresql.
Not reasonably no.
- Since in postgresql (or may be other also), when a database is
created, a path to a directory is given in
Hi ,
I have a question, I am suppose to create database with limited size. Is there
any way I can set limit to my database created in postgresql.
As per my surfing through various blogs, I found, its not possible
directly.This is my approach please let me know if I am going right:
- Since in
Michael Goldner <[EMAIL PROTECTED]> writes:
> On 11/5/07 12:19 AM, "Tom Lane" <[EMAIL PROTECTED]> wrote:
>> It might be interesting to look at stats such as
>> select sum(length(data)) from pg_largeobject;
>> to confirm that your 100GB estimate for the data payload is accurate.
> That select retur
On 11/5/07 12:19 AM, "Tom Lane" <[EMAIL PROTECTED]> wrote:
> Michael Goldner <[EMAIL PROTECTED]> writes:
>> The pg_largeobject table, however, seems a bit odd:
>
>> INFO: vacuuming "pg_catalog.pg_largeobject"
>> INFO: index "pg_largeobject_loid_pn_index" now contains 105110204 row
>> version
Michael Goldner <[EMAIL PROTECTED]> writes:
> The pg_largeobject table, however, seems a bit odd:
> INFO: vacuuming "pg_catalog.pg_largeobject"
> INFO: index "pg_largeobject_loid_pn_index" now contains 105110204 row
> versions in 404151 pages
> DETAIL: 778599 index row versions were removed.
>
On 11/4/07 8:26 PM, "Tom Lane" <[EMAIL PROTECTED]> wrote:
> "Michael Goldner" <[EMAIL PROTECTED]> writes:
>> I have a database with a single table that includes an oid reference to a
>> large object. After loading 100GB of large objects using lo_import(), I
>> find that my total database size has
"Michael Goldner" <[EMAIL PROTECTED]> writes:
> I have a database with a single table that includes an oid reference to a
> large object. After loading 100GB of large objects using lo_import(), I
> find that my total database size has grown by about 270GB. What is the
> reason for the difference
I'm running postgresql 8.1.8 on RHEL4.
I have a database with a single table that includes an oid reference to a
large object. After loading 100GB of large objects using lo_import(), I
find that my total database size has grown by about 270GB. What is the
reason for the difference in space usage
> Assuming that you are running Postgres on a linux system, you could do
> the following:
>
> 1) Create a partition with quotas enabled (via standard linux OS
> procedures). The postgres user is the user for which quotas should be
> enforced since postgresql always runs under the postgres uid.
>
On Mon, 2006-11-06 at 16:29 -0600, Nikola Radakovic wrote:
> Setting user's quota on my linux machine wont affect database
> quota.It will have impact on users directories.So, it must
> be a trick how to set PostgreSQL quota. Or how to link PostgreSQL
> database with directories which already have
On Mon, 2006-11-06 at 16:29, Nikola Radakovic wrote:
> Setting user's quota on my linux machine wont affect database
> quota.It will have impact on users directories.So, it must
> be a trick how to set PostgreSQL quota. Or how to link PostgreSQL
> database with directories which already have set qu
Setting user's quota on my linux machine wont affect database
quota.It will have impact on users directories.So, it must
be a trick how to set PostgreSQL quota. Or how to link PostgreSQL
database with directories which already have set quotas.
On Mon, 2006-11-06 at 16:52 -0500, Mike Goldner wro
> I appreciate your help, You don't understand me because my English is
> awful.
> I would try to paraphrase the sentence-maybe I succeed to correctly
> express myself.I want to limit database space for each database user on
> my system.For example, One user can hold one or more databases, but I
>
Nikola,
I'm not exactly sure what you are asking.
The size of the database is usually determined by the amount of data
stored and not determined beforehand.
Are you refering of "tablespaces", as other DBMSs use them? If so,
Postgres has a tablespace command, but it simply points to a filesy
> I would be very grateful if someone could answer me,
> where to find instructions how to set the size ( in megabytes ) for
> particular database.
I don't understand the question, are you looking to limit the size of your
database?
Regards,
Richard Broersma Jr.
---(e
select pg_database_size('')/1024/1024;http://www.postgresql.org/docs/8.1/interactive/functions-admin.html
On 11/6/06, Nikola Radakovic <[EMAIL PROTECTED]> wrote:
Dear community,I would be very grateful if someone could answer me,where to find instructions how to set the size ( in megabytes ) forpar
Dear community,
I would be very grateful if someone could answer me,
where to find instructions how to set the size ( in megabytes ) for
particular database.
best regards,
N.Radakovic
---(end of broadcast)---
TIP 1: if posting/reading through Us
/R
- Original Message -
From:
hubert depesz
lubaczewski
To: Roger Strandberg / Hamsta
Cc: pgsql-admin@postgresql.org
Sent: Saturday, October 22, 2005 8:05
AM
Subject: Re: [ADMIN] Database size, and
table size
On 10/22/05, Roger Strandberg /
Hamsta <[EMAIL
On 10/22/05, Roger Strandberg / Hamsta <[EMAIL PROTECTED]> wrote:
I wondering about file size of a
table.
dont wonder :) install dbsize module from postgresql contrib, and check.
depesz
Hi.
I wondering about file size of a
table.
The table has 43000 pages and in documentation is
say's its around 8kb.
It makes it supose to be around 336Mb on
disk.
The table is simple just:
org_no varchar (12)
Name varachar(225)
But when i create a tablespace on a mfs disk
and just load
After a long battle with technology, [EMAIL PROTECTED], an earthling, wrote:
> I need a reliable way to determine the overall size of our database.
> Recently, I started using the database_size() function from the dbsize
> contrib.
>
> Everything seems to work great until I need to delete records.
On Fri, Jul 01, 2005 at 09:30:50AM -0400, [EMAIL PROTECTED] wrote:
>
> I would expect the database size to decrease after the VACUUM.
Note what the documentation says about VACUUM and recovering disk
space:
http://www.postgresql.org/docs/8.0/static/maintenance.html#VACUUM-FOR-SPACE-RECOVERY
"Th
Hello All,
I need a reliable way to determine the overall size of our database.
Recently, I started using the database_size() function from the dbsize
contrib.
Everything seems to work great until I need to delete records.
After I DELETE records, the pg_autovacuum daemon kicks in an runs a VACUUM
I have recently inherited a Postgres 7.2 DB. I noticed that the size of the database
on the disk is about 100 times the size of the nightly dumps that get done. I looked
into it and realized that after millions of rows are deleted each month there was no
vacuum full performed on the DB. I als
Title: Database Size Limiting
Is there a way to limit the size that an individual database can take up?
My understanding is that all your databases go into a file system which is your ‘catalog cluster’.
But all the databases can grow until that filesystem is full.
Is there a way to limit h
Hi Robert
Thanks for the good start, it worked without a hitch in 7.2. :) So
that query lists the size (in kilobytes?) all of the relations and the
index's of the relations as well?
As you can see in the result header it gives the size in kb. Caution 1:
The script is written a little dirty. I
Oli Sennhauser wrote:
Hi Robert
I'm hoping to find a easy way to find the disk space used by each
database on a given postgres v7.2 server - I've been looking through
the docs and have seen some references to oid2name, but that doesn't
really help my situation.
This script gives you the used
Hi Robert
I'm hoping to find a easy way to find the disk space used by each
database on a given postgres v7.2 server - I've been looking through
the docs and have seen some references to oid2name, but that doesn't
really help my situation.
This script gives you the used size per object. Unfortu
I'm hoping to find a easy way to find the disk space used by each
database on a given postgres v7.2 server - I've been looking through the
docs and have seen some references to oid2name, but that doesn't really
help my situation.
Any suggestions?
Robert Young
---(end of
In the contrib directory exists the database_size function (dbsize
directory, i think) ...
And if you want to automate the process of retrieving all your databases
size
http://www.brasileiro.net:8080/postgres/cookbook/view-one-recipe.adp?recipe_id=15493
Anagha Joshi wrote:
Hi,
How can I know
Hi,
How can I know size of the specific database in Postgres?
Thx. in advance.
-Anagha
Elielson Fontanezi wrote:
> Hello folks!
>
> Is there any way to know the database size of a postgres 7.2 db?
Yes, use contrib/oid2name and 'du', or contrib/dblink.
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED] | (610) 853-3000
Hello folks!
Is there any way to know the database size of a postgres 7.2 db?
Thanks!
Elielson,
---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMA
65 matches
Mail list logo
