Re: pg_log

Поиск
Список
Период
Сортировка
От The Hermit Hacker
Тема Re: pg_log
Дата
Msg-id Pine.BSF.4.21.0010260110090.344-100000@thelab.hub.org
обсуждение исходный текст
Ответ на pg_log  (Sylvain Simard <sylvain@luxolith.com>)
Список 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@luxolith.com
>
>
>

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

В списке pgsql-bugs по дате отправления:

Предыдущее
От: pgsql-bugs@postgresql.org
Дата:
Сообщение: Select where (upper(xy)~'.CH'); ..matches also SPACE CH
Следующее
От: Sean Kelly
Дата:
Сообщение: Re: Updating multiple bool values crashes backend