You can check the running processes and grep aotovacuum.
You should see a launcher process which is always running.
If you use pgAdmin you can also look at the table statistics from the
GUI and see when was the last time autovacuum or autoanalyze ran on each
table.
From: pgsql-admin-ow...@
Thanks raghu ram for your immediate response,
i will try this path too along with my team and i will come back if any
issues.
Thanks
Senthil
_
From: raghu ram [mailto:raghuchenn...@gmail.com]
Sent: Friday, April 01, 2011 8:57 PM
To: Senthil Kumar G
Cc: pgsql-admin@postgresql.org
On Fri, Apr 1, 2011 at 5:41 PM, bilal ghayyad wrote:
> Hi All;
>
> I read that I have to set the tcpip_socket = True in postgresql.conf file,
> but when I am setting it, the postgresql database failed to start.
>
> My linux is fedora core 10, so what I have to do?
>
> tcpip_socket = True
>
Coul
Hi Kevin:
Thanks for your quick response.
I will try out this and come back if issue was not resolved still.
Thanks
Senthil
-Original Message-
From: Kevin Grittner [mailto:kevin.gritt...@wicourts.gov]
Sent: Friday, April 01, 2011 8:49 PM
To: pgsql-admin@postgresql.org; Senthil Kumar G
S
On Fri, Apr 1, 2011 at 8:34 PM, Senthil Kumar G wrote:
> Hi
>
>
>
> I am upgrading my staging environment from postgresql 8.2.3 to 9.0.3.
>
>
>
> I was able to do successfully.
>
>
>
> But, when i try to import the database which is created in 8.2.0 version to
> 9.0.3 version environment, i am g
"Senthil Kumar G" wrote:
> I am upgrading my staging environment from postgresql 8.2.3 to
> 9.0.3.
>
> I was able to do successfully.
> [errors while applying dump to new database]
> What could be the reason? What should i do to resolve this?
The recommended upgrade technique is to us pg_
Hi
I am upgrading my staging environment from postgresql 8.2.3 to 9.0.3.
I was able to do successfully.
But, when i try to import the database which is created in 8.2.0 version to
9.0.3 version environment, i am getting following error.
ERROR: constraint "" for relation ""
Rajendra prasad wrote:
> Jerry Sievers wrote:
>> Rajendra prasad writes:
>>> I have 50 GB data base folder for postgres. Out of 50 GB 20 GB
>>> has been occupied by 8 indexes of a single table by growing upto
>>> 2 GB each.
There's a good chance you don't need all of those indexes or that
yo
Rajendra prasad wrote:
> I am not doing vacuum atall.
Please run the query on this page and post the results:
http://wiki.postgresql.org/wiki/Server_Configuration
My hope is that you are on a recent version of PostgreSQL with
autovacuum taking care of things by default.
-Kevin
--
Sent
Hi,
I am not doing vacuum atall.
Prasad
On Fri, Apr 1, 2011 at 12:06 PM, scorpda...@hotmail.com <
scorpda...@hotmail.com> wrote:
> How recent is the vacuum in this DB?
>
>
>
> - Reply message -
> From: "Rajendra prasad"
> Date: Thu, Mar 31, 2011 11:01 pm
> Subject: [ADMIN] Index size g
Hi,
Thank you for the info. I am doing the reindex for an individual index. And
i am doing this in the live server and apps are connecting to it at the same
time. Is this not correct?
I am new to postgres. Kindly brief me the steps which i need to follow.
Prasad
On Fri, Apr 1, 2011 at 1:28 PM,
Selva manickaraja wrote:
> Since the production database is running, I plan to do now is
> this
>
> 1. Set archive_timeout = 20m (Does the change require db restart
> to take effect?)
You'd better make that '20min'. Reload should suffice.
> 2. Set autovacuum=on and track_count=on (Does t
"Anibal David Acosta" wrote:
> I have two postgres 9.0 database both can be modified and both
> must have same information.
>
> In case of collision (same row changed in both) must win the most
> recent.
If latency issues don't preclude it, pgpool might work for you.
-Kevin
--
Sent via pg
--- On Fri, 1/4/11, Kenneth Marshall wrote:
> >
> > Just testing some new hardware on 9.0.3 and have
> restored one of our dumps from 8.4.7. What I'm seeing
> is although table sizes are the same, indexes are a lot
> bigger, approx 50%.
> >
> > I've done a search and so far can't find anything
On Fri, Apr 01, 2011 at 01:46:03PM +0100, Glyn Astill wrote:
> Hey Guys,
>
> Just testing some new hardware on 9.0.3 and have restored one of our dumps
> from 8.4.7. What I'm seeing is although table sizes are the same, indexes
> are a lot bigger, approx 50%.
>
> I've done a search and so far
Hello.
I have two postgres 9.0 database both can be modified and both must have
same information.
In case of collision (same row changed in both) must win the most recent.
Thanks.
Hey Guys,
Just testing some new hardware on 9.0.3 and have restored one of our dumps from
8.4.7. What I'm seeing is although table sizes are the same, indexes are a lot
bigger, approx 50%.
I've done a search and so far can't find anything, but have default fillfactors
changed? Or is it someth
On Fri, Apr 1, 2011 at 1:04 PM, Gerhard Hintermayer
wrote:
> I managed to set up a streaming replication with 9.0.3. This works like a
> charm.
> When I pull the trigger - I mean create the trigger file ;-) - I find
> the following entries in the server log, is this normal or am I doing
> somethi
Hi All;
I read that I have to set the tcpip_socket = True in postgresql.conf file, but
when I am setting it, the postgresql database failed to start.
My linux is fedora core 10, so what I have to do?
tcpip_socket = True
Regards
Bilal
--
Sent via pgsql-admin mailing list (pgsql-admi
I managed to set up a streaming replication with 9.0.3. This works like a charm.
When I pull the trigger - I mean create the trigger file ;-) - I find
the following entries in the server log, is this normal or am I doing
something nasty ?
[ @]LOG: streaming replication successfully connected to p
Rajendra prasad writes:
> Hi,
>
> I have 50 GB data base folder for postgres. Out of 50 GB 20 GB has
> been occupied by 8 indexes of a single table by growing upto 2 GB
> each. I googled and got the info that reindex will help brining back
> the actual size of the index. But the disk has only 4 G
On Thu, Mar 31, 2011 at 3:37 PM, Anal Dey wrote:
> I need a help on restoring backup which was taken under a linux machine
> with
> the below command
>
> pg_dump mydb > /myhome/backup/mydb_backup.pgdump
>
> now I want to restore the backup (my_db_backup.pgdume) file under my
> windows
> machine
How recent is the vacuum in this DB?
- Reply message -
From: "Rajendra prasad"
Date: Thu, Mar 31, 2011 11:01 pm
Subject: [ADMIN] Index size growing
To:
Hi,
I have 50 GB data base folder for postgres. Out of 50 GB 20 GB has been
occupied by 8 indexes of a single table by growing upto
Hi,
I have 50 GB data base folder for postgres. Out of 50 GB 20 GB has been
occupied by 8 indexes of a single table by growing upto 2 GB each. I googled
and got the info that reindex will help brining back the actual size of the
index. But the disk has only 4 GB left . Due to this, when i run rein
Hi,
I need a help on restoring backup which was taken under a linux machine with
the below command
pg_dump mydb > /myhome/backup/mydb_backup.pgdump
now I want to restore the backup (my_db_backup.pgdume) file under my windows
machine can any one kindly explain me the process to restore this.
I
You can ignore contents of pg_xlog is you are running WAL archiving. You can
skip postmaster.pid and pg_log but make sure that you recreate pg_log in
the target.
On Fri, Apr 1, 2011 at 3:13 PM, A B wrote:
> Hello.
>
> I just wanted to check with you, the experts, on what directories to
> includ
Hello.
I just wanted to check with you, the experts, on what directories to
include in the basebackup (following
http://www.postgresql.org/docs/8.4/static/continuous-archiving.html)
I should include these:
base/
global/
pg_clog/
pg_multixact/
pg_stat_tmp/
pg_subtrans/
pg_tblspc/
pg_twophase/
PG_
27 matches
Mail list logo
