Re: WAL - Mailing list pgsql-general

From Bruce Momjian
Subject Re: WAL
Date
Msg-id 200108202052.f7KKqE908119@candle.pha.pa.us
Whole thread Raw
In response to WAL  (Fernando Ipar <ipar@ediguay.com.uy>)
List 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@candle.pha.pa.us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

pgsql-general by date:

Previous
From: "Ryan C. Bonham"
Date:
Subject: ERROR: relation_info: Relation 41069 not found
Next
From: Doug McNaught
Date:
Subject: Re: Problems with installation v 7.1.2