From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Fernando Ipar <ipar(at)ediguay(dot)com(dot)uy> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: WAL |
Date: | 2001-08-20 20:52:14 |
Message-ID: | 200108202052.f7KKqE908119@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
> Hi, this is my first message to the list.
> I've been looking for some documentation regarding WAL
> configuration. Particulary, i want to know if there's
> a way to inhibit WAL for a certain table or for
> certain periods of time (i.e., during batch loads,
> when i don't really care for transaction logging since
> if anything goes wrong i can just restart the whole
> process without affecting the integrity of the table).
>
> I've searched the archives before asking and the only
> thing related to this was found on the hackers list,
> it explained how to limit the size and number of
> the WAL files, but it involved a patch to the
> code. I don't have a problem with patchin the source
> if this is the last resource, but it would be
> great if this could be done with a configuration
> directive (i didn't find anything related to this
> on the admin manual so this is probably impossible)
> or with a SQL command.
7.1.3 is only going to use a few log segments no matter how large your
transaction is. It still does the writes, though.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2001-08-20 20:56:53 | Re: how do you recover a postgresql online backup |
Previous Message | Evan Zane Macosko | 2001-08-20 20:33:29 | Re: Problems with UPDATE |