From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
Cc: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Simon Riggs <simon(at)2ndQuadrant(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Enabling archive_mode without restart |
Date: | 2008-10-31 17:14:30 |
Message-ID: | 5835.1225473270@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> writes:
> archive_mode = on disables the optimization to skip WAL-logging when
> loading into a new table that was created in the same transaction.
... and affects a whole bunch of other behaviors too, in processes all
across the database that could not possibly adopt a new setting
synchronously. That's exactly why it was made a postmaster-start option
to begin with. Simon's given no argument at all why it would be safe to
flip it on-the-fly.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Gregory Stark | 2008-10-31 17:14:31 | Re: Changing the result of ExecutorRun |
Previous Message | Hitoshi Harada | 2008-10-31 17:10:55 | Re: Window Functions: patch for CommitFest:Nov. |