Skip site navigation (1) Skip section navigation (2)

Re: pg_log

From: The Hermit Hacker <scrappy(at)hub(dot)org>
To: Sylvain Simard <sylvain(at)luxolith(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: pg_log
Date: 2000-10-26 04:11:44
Message-ID: Pine.BSF.4.21.0010260110090.344-100000@thelab.hub.org (view raw or flat)
Thread:
Lists: pgsql-bugs
the only way of initializing it (to the best of my knowledge) is to backup
your databases (pg_dump) and a re-initdb of the database ... one person
recently rm'd the pg_log and found out just how disasterous that is :(

btw, would heavily recomment upgrading to 7.0.2 while you are at it, which
has more fixes and improvements then I'd care to recount in an email ...

On Wed, 25 Oct 2000, Sylvain Simard wrote:

> Hi my name is Sylvain
> I use Postgres 6.5.3-3
> Why is the pg_log???
> 
> I have a program than run 24hrs/day and many transaction has been send
> to postgres
> eg (select, insert, update, vacuum, (begin work-commit work)...)
> 
> At begin, with a new database the pg_log are 40k
> After many days my pg_log is come 3884k
> 
> It's possible to initialize it? If yes how...
> It's possible to do anything to don't pg_log come bigger and bigger...
> 
> thanks a lots in advance for your help
> Sylvain
> sylvain(at)luxolith(dot)com
> 
> 
> 

Marc G. Fournier                   ICQ#7615664               IRC Nick: Scrappy
Systems Administrator @ hub.org 
primary: scrappy(at)hub(dot)org           secondary: scrappy(at){freebsd|postgresql}.org 


In response to

  • pg_log at 2000-10-25 21:02:12 from Sylvain Simard

pgsql-bugs by date

Next:From: pgsql-bugsDate: 2000-10-26 04:29:49
Subject: Select where (upper(xy)~'.CH'); ..matches also SPACE CH
Previous:From: Tom LaneDate: 2000-10-26 03:15:31
Subject: Re: Slack7.1/linux.2.4 compile error: storage size of `semun' isn't known

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group