[GENERAL] DNN Postgres Data Provider
Our company is moving toward developing web applications in the DNN 3 (Dot Net Nuke) framework. We currently have several applications supported by Postgres/PostGIS due to the spatial requirements. To ideally bridge these two technologies together would be to develop a DNN DataProvider assembly. I'm wondering if anyone has put forth any effort toward such a cause? Thank you, Randy rhow [at] i3 [dot] com
[GENERAL] FW: Serverlog 100GB
Greetings, We're running PostGres on linux, version 8.1.x. on a new server for a few weeks. And the serverlog just consumed the rest of the disk space - 100GB log file. Wow, that's a personal record. I'm not a Linux guru so if you could point me in the right direction I'd appreciate it. How do I go about changing the "serverlog" file settings? The only reference I've found to serverlog is: su -c 'pg_ctl start -D /usr/local/pgsql/data -l serverlog' postgres. Thanks, Randy
Re: [GENERAL] FW: Serverlog 100GB
Thanks Tom, http://www.postgresql.org/docs/8.1/interactive/logfile-maintenance.html I'll go over this documentation. Thanks again Randy -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Tom Lane Sent: Thursday, August 24, 2006 10:37 PM To: Randy How Cc: pgsql-general@postgresql.org Subject: Re: [GENERAL] FW: Serverlog 100GB "Randy How" <[EMAIL PROTECTED]> writes: > We're running PostGres on linux, version 8.1.x. on a new server for a > few weeks. And the serverlog just consumed the rest of the disk space > - 100GB log file. Wow, that's a personal record. Perhaps choose less verbose logging settings? But really the correct answer to this is to set up a logfile rotation schedule, which you can easily do with either syslog or redirect_stderr log methods. I'd lean to the latter myself. regards, tom lane ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
Re: [GENERAL] FW: Serverlog 100GB
= off #debug_pretty_print = off #log_connections = off #log_disconnections = off #log_duration = off #log_line_prefix = '' # Special values: # %u = user name # %d = database name # %r = remote host and port # %h = remote host # %p = PID # %t = timestamp (no milliseconds) # %m = timestamp with milliseconds # %i = command tag # %c = session id # %l = session line number # %s = session start timestamp # %x = transaction id # %q = stop here in non-session #processes # %% = '%' # e.g. '<%u%%%d> ' #log_statement = 'none' # none, mod, ddl, all #log_hostname = off -Original Message- From: Randy How [mailto:[EMAIL PROTECTED] Sent: Friday, August 25, 2006 8:52 AM To: 'Tom Lane' Cc: 'pgsql-general@postgresql.org' Subject: RE: [GENERAL] FW: Serverlog 100GB Thanks Tom, http://www.postgresql.org/docs/8.1/interactive/logfile-maintenance.html I'll go over this documentation. Thanks again Randy -----Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Tom Lane Sent: Thursday, August 24, 2006 10:37 PM To: Randy How Cc: pgsql-general@postgresql.org Subject: Re: [GENERAL] FW: Serverlog 100GB "Randy How" <[EMAIL PROTECTED]> writes: > We're running PostGres on linux, version 8.1.x. on a new server for a > few weeks. And the serverlog just consumed the rest of the disk space > - 100GB log file. Wow, that's a personal record. Perhaps choose less verbose logging settings? But really the correct answer to this is to set up a logfile rotation schedule, which you can easily do with either syslog or redirect_stderr log methods. I'd lean to the latter myself. regards, tom lane ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings ---(end of broadcast)--- TIP 1: 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
