Re: [ADMIN] Table Partitioning

Ken, Table partitioning doesn't really exist, to the best of my knowledge, but tablespaces, which are new to 8.0, allow for partitioning of data (individual tables, indexes) across multiple locations on disk. See http://www.postgresql.org/docs/8.0/static/sql-createtablespace.html -tfo -- T

Re: [ADMIN] Pg_autovacuum script.

A while back, I wrote this: http://www.sitening.com/auto_pg_autovacuum While not exactly an init script, it sanely avoids multiply starting pg_autovacuum. Then I did this: http://www.sitening.com/pgautovacuum which is a proper init script. Thanks for prompting me to post it! Now there are

Re: [ADMIN] testing pgpool

Is postgres actually running? And is your pg_hba.conf file configured to allow local UNIX socket connections? -tfo -- Thomas F. O'Connell Co-Founder, Information Architect Sitening, LLC http://www.sitening.com/ 110 30th Avenue North, Suite 6 Nashville, TN 37203-6320 615-260-0005 On Mar 16, 200

Re: [ADMIN] IMPORTANT: two new PostgreSQL security problems found

I put together a little Perl script (which assumes proper installation of both DBI and DBD::Pg and that template1 exists) that takes care of the character conversion vulnerability: http://www.sitening.com/postgresql-update-2005-1 I've run this on my development servers, and it seems to have had

Re: [ADMIN] [ANNOUNCE] IMPORTANT: two new PostgreSQL security problems found

Considering that this is a security-related system catalog update, is there any way of providing some sort of signature for a message like this such that the community can feel that issuing some arcane commands as a superuser won't open a hole rather than close one? This is the first time I've

Re: [ADMIN] Killing Processes

enue North, Suite 6 Nashville, TN 37203-6320 615-260-0005 On Apr 23, 2005, at 11:16 AM, Michael Fuhr wrote: On Sat, Apr 23, 2005 at 10:58:46AM -0500, Thomas F.O'Connell wrote: It is generally not recommended that you kill processes with anything stronger than HUP, which is (I believe) what kill s

Re: [ADMIN] Pg_autovacuum script.

A while back, I wrote this: http://www.sitening.com/auto_pg_autovacuum While not exactly an init script, it sanely avoids multiply starting pg_autovacuum. Then I did this: http://www.sitening.com/pgautovacuum which is a proper init script. Thanks for prompting me to post it! Now there are some op

Re: [ADMIN] Limited to 100 connections

max_connections is a setting that can only be set at server start. Are you restarting postgres after you change the setting in postgresql.conf? -tfo -- Thomas F. O'Connell Co-Founder, Information Architect Sitening, LLC Strategic Open Source: Open Your i™ http://www.sitening.com/ 110 30th Avenue

Re: [ADMIN] testing pgpool

Is postgres actually running? And is your pg_hba.conf file configured to allow local UNIX socket connections? -tfo -- Thomas F. O'Connell Co-Founder, Information Architect Sitening, LLC http://www.sitening.com/ 110 30th Avenue North, Suite 6 Nashville, TN 37203-6320 615-260-0005 On Mar 16, 2005,

Re: [ADMIN] Too many clients----A big problem for my team

Well, first of all, max_connections can only be set at server start. Are you restarting postgres when you do "trial and error changes"? Secondly, 5 users can still manage to make multiple connections. You can use ps to see how many connections are active at any given time. http://www.postgresql

Re: [ADMIN] dropdb: database removal failed: ERROR: database "database_name" is being accessed by other users

pkill -f 'postgres: postgres ' Much cleaner than the previous recipe for those with pkill. -tfo -- Thomas F. O'Connell Co-Founder, Information Architect Sitening, LLC http://www.sitening.com/ 110 30th Avenue North, Suite 6 Nashville, TN 37203-6320 615-260-0005 ---(end of bro