[SQL] ANNOUNCE: Bricolage 1.3.3

[David Wheeler]

The Bricolage developers are pleased to announce the release of 
Bricolage version 1.3.3!

This the release candidate for Bricolage verion 1.4.0, and is 
considered feature-complete. Nearly 50 new features have been added 
since the 1.2.2 release, and over 80 bugs fixed. Barring any unforseen 
major bugs cropping up, 1.4.0 will be released within a week of this 
release. Please feel give it a try, and report any issues to the 
Bricolage Bugzilla database, at
http://bugzilla.bricolage.cc/.

Learn more about Bricolage and download it from the Bricolage home page,
http://bricolage.cc/.

General description:

Bricolage is a full-featured, enterprise-class content management 
system. It
offers a browser-based interface for ease-of use, a full-fledged 
templating
system with complete programming language support for flexibility, and 
many
other features. It operates in an Apache/mod_perl environment, and uses 
the
PostgreSQL RDBMS for its repository.

Enjoy!

--The Bricolage Team


---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly

Re: [SQL] [Dbdpg-general] [ANNOUNCE] pgtop, display PostgreSQL processes in `top' style

[David Wheeler]

On Apr 30, 2005, at 15:10 , Cosimo Streppone wrote:
1) is it possible to know Pg backend uptime with
   SQL queries? Or must I look at postmaster.pid file?
   or even something else?
I think that the PID file is your best bet.
2) how can I know the ip addresses/hostnames of clients
   connecting to server?
I believe that that information is in pg_stat_activity. See:
  http://www.postgresql.org/docs/current/static/monitoring.html
3) Is there a way to know the number of queries performed
   against Pg backend (by each client)? Can I distinguish
   between selects / updates / inserts / copy / ... ?
I think so, but you have to enable some postgresql.conf settings to  
get that information logged.

  http://www.postgresql.org/docs/8.0/static/runtime-config.html
Regards,
David
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster