Re: [ADMIN] pg_ctl: server does not shut down

2010-10-28 Thread Gnanakumar
>> You can check if PITR is disabled by executing: >> SHOW archive_command; >> At a psql prompt. If that's empty, then you turned it off, and it isn't >> involved in the shutdown issue you have anymore. > Yes, I could see empty value here. >> Take a look at what processes are still running again

[ADMIN] Forced quiesce

2010-10-28 Thread Little, Douglas
Hi, We're having to vacuum full the system tables everyday due to the number of temp table drop/creates. We're finding that if anyone tries to execute a job during the maintenance period, it often hangs the db. Is there a way that we can force the db to quiesce? Or lock out users. Luckly, mo

Re: [ADMIN] Forced quiesce

2010-10-28 Thread Kenneth Marshall
On Thu, Oct 28, 2010 at 07:39:19AM -0500, Little, Douglas wrote: > Hi, > We're having to vacuum full the system tables everyday due to the number of > temp table drop/creates. > We're finding that if anyone tries to execute a job during the maintenance > period, it often hangs the db. > > Is th

Re: [ADMIN] Forced quiesce

2010-10-28 Thread Plugge, Joe R.
Could you roll in a temporary pg_hba.conf, issue the pg_ctl reload command to reread that and then identify those ips using ps, and kill -TERM them? After your maintenance, rotate back in your full pg_hba.conf and reload it. From: pgsql-admin-ow...@postgresql.org [mailto:pgsql-admin-ow...@p

Re: [ADMIN] Forced quiesce

2010-10-28 Thread Sergey Konoplev
Hi, David Fetter has an article about the issue like your. He describes the situation with DROP DATABASE but it could easily be adapted for VACUUM. Here is the link http://people.planetpostgresql.org/dfetter/index.php?/archives/63-Kick-em-out,-and-keep-em-out!.html On 28 October 2010 16:39, Littl

[ADMIN] advantages of multiple db's

2010-10-28 Thread Little, Douglas
Hi, We have 1 db with everything in our entire enterprise in it (It's a data warehouse). What are some of the disadvantages of using multiple db's? Can we join across db's? Doug Little Sr. Data Warehouse Architect | Enterprise Data Management | Orbitz Worldwide 500 W. Madison, Suite 1000 Chi

Re: [ADMIN] advantages of multiple db's

2010-10-28 Thread Plugge, Joe R.
Postgres does not natively do cross joins, you can however use a third party tool called dblink From: pgsql-admin-ow...@postgresql.org [mailto:pgsql-admin-ow...@postgresql.org] On Behalf Of Little, Douglas Sent: Thursday, October 28, 2010 8:35 AM To: pgsql-admin@postgresql.org Subject: [ADMIN] a

Re: [ADMIN] advantages of multiple db's

2010-10-28 Thread Sergey Konoplev
HI, On 28 October 2010 17:34, Little, Douglas wrote: > Hi, > > > > We have 1 db with everything in our entire enterprise in it (It’s a data > warehouse). What are some of the disadvantages of using multiple db’s? > > > > Can we join across db’s? > I think this article is a good start point to

Re: [ADMIN] Using LDAP with postgresql 8.2

2010-10-28 Thread Kieren Scott
Hi, I've setup LDAP on Postgresql 8.3.6 by adding the following line to pg_hba.conf. My Active Directory has a group called 'users group' which contains an entry for user pgtest. host all pgtestxx.xxx.x.x/xx ldap "ldap://server.mydomain.com:389/basedn;cn=;,ou=users group,dc=mydom

[ADMIN] problem with rules

2010-10-28 Thread Uwe Bartels
Hi, i'm trying to reorganize a big table without having a downtime at all. I'm trying to realize this via partitioning and rules. - step 1 preparation create table uglybloatedtable (id bigserial, textfield text, primary key(id)); INSERT INTO uglybloatedtable (textfield) values (''); INSERT INTO u