Re: [ADMIN] pg_attribute size

2009-10-26 Thread Anj Adu
I am guessing the analyze helped the pgadmin data-dictionary query planning..The vacuum will help with space re-use. the size is not smaller as I did not do a vacuum full. On Mon, Oct 26, 2009 at 4:27 PM, Scott Marlowe wrote: > On Mon, Oct 26, 2009 at 3:29 PM, Anj Adu wrote: >> We have several

Re: [ADMIN] pg_attribute size

2009-10-26 Thread Scott Marlowe
On Mon, Oct 26, 2009 at 3:29 PM, Anj Adu wrote: > We have several partitioned tables that get dropped every day ..We do > not do autovacuum as it is an IO hog (and most tables are dropped > anyways..and the large tables are never updated).. 1: autovac can be adjusted to use much less IO than regu

Re: [ADMIN] pg_attribute size

2009-10-26 Thread Naomi Walker
We dump and vacuum every database every evening, so we can control when the vacuums occur. How does one vacuum the system catalogs? By each tablename pg_*? Thanks, Naomi > > On Mon, Oct 26, 2009 at 3:46 PM, Tom Lane wrote: >> Anj Adu writes: >>> We have several partitioned tables that get dr

Re: [ADMIN] Warm standby problems

2009-10-26 Thread Tom Lane
"David F. Skoll" writes: > Tom Lane wrote: >> No; there's no WAL change between 8.3.7 and 8.3.8. What seems more >> likely is that you're somehow shipping the WAL files before they're >> quite finished. > So unless there's a possibility that the master server invokes our archive > script before

Re: [ADMIN] duplicate key violated errors

2009-10-26 Thread Tom Lane
dinesh writes: > I have a table, which has over 3 million rows. We have both a unique > constraint ( which creates implicit index) as well as a regular unique > index on the same column. We had to put the unique constraint because > duplicate values > were getting inserted to the table in spite

Re: [ADMIN] pg_attribute size

2009-10-26 Thread Anj Adu
Agreed... Thank you On Mon, Oct 26, 2009 at 3:46 PM, Tom Lane wrote: > Anj Adu writes: >> We have several partitioned tables that get dropped every day ..We do >> not do autovacuum as it is an IO hog (and most tables are dropped >> anyways..and the large tables are never updated).. > > If you'

Re: [ADMIN] pg_attribute size

2009-10-26 Thread Tom Lane
Anj Adu writes: > We have several partitioned tables that get dropped every day ..We do > not do autovacuum as it is an IO hog (and most tables are dropped > anyways..and the large tables are never updated).. If you're not going to run autovacuum then that means *you* must take responsibility for

[ADMIN] duplicate key violated errors

2009-10-26 Thread dinesh
Hi All: I have a table, which has over 3 million rows. We have both a unique constraint ( which creates implicit index) as well as a regular unique index on the same column. We had to put the unique constraint because duplicate values were getting inserted to the table in spite of the regular

Re: [ADMIN] pg_attribute size

2009-10-26 Thread Anj Adu
We have several partitioned tables that get dropped every day ..We do not do autovacuum as it is an IO hog (and most tables are dropped anyways..and the large tables are never updated).. I however did a plain vacuum analyze and that fixed the problem with tools(e.g pgadmin) that accessed the data

Re: [ADMIN] Warm standby problems

2009-10-26 Thread David F. Skoll
Tom Lane wrote: > No; there's no WAL change between 8.3.7 and 8.3.8. What seems more > likely is that you're somehow shipping the WAL files before they're > quite finished. I doubt it. Our archive_command works like this: 1) scp the file over to the backup server as root. It's stored in a fil

Re: [ADMIN] Warm standby problems

2009-10-26 Thread Tom Lane
"David F. Skoll" writes: > I have one PostgreSQL 8.3 machine feeding WAL files to another PostgreSQL 8.3 > machine that's running in recovery mode. However, fairly often (every > few days), the standby machine breaks out of recovery mode with log messages > like: > 2009-10-23 21:47:40 EDT LOG:

[ADMIN] Warm standby problems

2009-10-26 Thread David F. Skoll
Hi, I have one PostgreSQL 8.3 machine feeding WAL files to another PostgreSQL 8.3 machine that's running in recovery mode. However, fairly often (every few days), the standby machine breaks out of recovery mode with log messages like: 2009-10-23 21:47:40 EDT LOG: incorrect resource manager data

Re: [ADMIN] WAL file compatibility

2009-10-26 Thread Tom Lane
Steve Crawford writes: > Tom Lane wrote: >> The source and destination servers have to be the same major PG release, >> same architecture (no 32-bit vs 64-bit for instance), and built with the >> same configure options. OS per se shouldn't matter, but you could >> easily get burnt on configure op

Re: [ADMIN] Permissions to schema

2009-10-26 Thread Scott Mead
2009/10/26 Eduardo Sá dos Reis > Hi, > > I have the structure on Postgre: > > *database*: dbGlobal > > *schema1:* sch_sist1 *owner *sch_sist1: john > > *schema2 *sch_sist2 *owner *sch_sist2: mary > > > I' m using pgAdmin III. > > Is there a way to avoid the mary to ac

[ADMIN] Permissions to schema

2009-10-26 Thread Eduardo Sá dos Reis
Hi, I have the structure on Postgre: database: dbGlobal schema1: sch_sist1 owner sch_sist1: john schema2 sch_sist2 owner sch_sist2: mary I' m using pgAdmin III. Is there a way to avoid the mary to access the schema sch_sist1 ? I don't want that mary see/access th

Fwd: [ADMIN] configuration kerberos in Postgre sql

2009-10-26 Thread rahimeh khodadadi
-- Forwarded message -- From: rahimeh khodadadi Date: Sun, Oct 25, 2009 at 4:55 PM Subject: Re: [ADMIN] configuration kerberos in Postgre sql To: Geoff Tolley I am new to kerberos. I need help Whether we define ank username for every users of postgresql in kadmin.local? or we