Hello:
Thank you all.
I have understood this.
Best Regards
2013/8/31 Kevin Grittner
> 高健 wrote:
>
> > So I think that in a mission critical environment, it is not a
> > good choice to turn full_page_writes on.
>
> If full_page_writes is off, your database can be corrupted in the
> event of
高健 wrote:
> So I think that in a mission critical environment, it is not a
> good choice to turn full_page_writes on.
If full_page_writes is off, your database can be corrupted in the
event of a crash of the hardware, OS, or VM (for example a power
failure). The only exception is if your enviro
Hello
Thanks for replying.
It is really a complicated concept.
So I think that in a mission critical environment , it is not a good choice
to turn full_page_writes on.
Best Regards
2013/8/27 Jeff Janes
> On Sun, Aug 25, 2013 at 7:57 PM, 高健 wrote:
> > Hi :
> >
> > Thanks to Alvaro! Sorry fo
On Sun, Aug 25, 2013 at 7:57 PM, 高健 wrote:
> Hi :
>
> Thanks to Alvaro! Sorry for replying lately.
>
> I have understood a little about it.
>
> But the description of full_page_write made me even confused. Sorry that
> maybe I go to another problem:
>
> It is said:
> http://www.postgresql.org/docs
On 08/26/2013 11:37 AM, Luca Ferrari wrote:
On Mon, Aug 26, 2013 at 4:57 AM, 高健 wrote:
But why "writes the entire content of each disk page to WAL "?
The documentation states that: "The row-level change data normally
stored in WAL will not be enough to completely restore such a page
during p
On Mon, Aug 26, 2013 at 4:57 AM, 高健 wrote:
> But why "writes the entire content of each disk page to WAL "?
>
The documentation states that: "The row-level change data normally
stored in WAL will not be enough to completely restore such a page
during post-crash recovery.". I guess that a mixed pa
Hi :
Thanks to Alvaro! Sorry for replying lately.
I have understood a little about it.
But the description of full_page_write made me even confused. Sorry that
maybe I go to another problem:
It is said:
http://www.postgresql.org/docs/9.2/static/runtime-config-wal.html#GUC-FULL-PAGE-WRITES
-
高健 escribió:
> ...
> Checkpoints are fairly expensive, first because they require writing out
> all currently dirty buffers, and second because they result in extra
> subsequent WAL traffic as discussed above.
> ...
>
> What confused me is that: (checkpoint)result in extra subsequent WAL
> traff
Hello:
Sorry for disturbing.
I have one question : Will checkpoint cause wal written happen?
I found the following info at:
http://www.postgresql.org/docs/9.2/static/wal-configuration.html
...
Checkpoints are fairly expensive, first because they require writing out
all currently dirty buffe
