Re: Need help understanding WAL and checkpoints - Mailing list pgsql-general

From drew_hunt1976@yahoo.co.jp
Subject Re: Need help understanding WAL and checkpoints
Date
Msg-id 325825.13507.qm@web4505.mail.ogk.yahoo.co.jp
Whole thread Raw
In response to Re: Need help understanding WAL and checkpoints  (Albe Laurenz <laurenz.albe@wien.gv.at>)
List pgsql-general
Hi Albe=0A=0A--- On Wed, 2013/2/6, Albe Laurenz <laurenz.albe@wien.gv.at> w=
rote:=0A=0A> drew_hunt wrote:=0A> > I'm trying to get my head around WAL an=
d checkpoints and need to ask a couple of questions before I=0A> > get a he=
adache.=0A> > =0A> > Firstly, I see the terms "WAL log", "WAL file" and "tr=
ansaction log" all over the place - are these=0A> > the same thing (i.e. fi=
les in the pg_xlog directory)?=0A> =0A> Usually they mean the same thing.=
=0A> For exact definitions, read=0A> http://www.postgresql.org/docs/current=
/static/continuous-archiving.html#BACKUP-ARCHIVING-WAL=0A> "WAL" consists o=
f a stream of "WAL records" and is physically=0A> represented as "WAL segme=
nt files" (in pg_xlog).=0A> =0A> > I'm a bit confused by this paragraph in =
the docs:=0A> > =0A> > "Checkpoints are points in the sequence of transacti=
ons at which it is guaranteed that the heap and=0A> > index data files have=
 been updated with all information written before the checkpoint. At checkp=
oint=0A> > time, all dirty data pages are flushed to disk and a special che=
ckpoint record is written to the log=0A> > file. (The changes were previous=
ly flushed to the WAL files.)"=0A> > =0A> > ( see: http://www.postgresql.or=
g/docs/current/static/wal-configuration.html )=0A> > =0A> > "a special chec=
kpoint record is written to the log file."=0A> > =A0=A0=A0 -> which log fil=
e is meant here?=0A> =0A> The WAL.=0A> =0A> > "The changes were previously =
flushed to the WAL files."=0A> > =A0=A0 -> does "previously" here mean "at =
a previous point in time" or "in previous PostgreSQL versions"?=0A> =0A> Th=
e former.=0A> =0A> > =A0=A0 -> at what point are changes flushed to WAL fil=
es?=0A> =0A> The change must be on disk in a WAL segment before the=0A> tra=
nsaction can commit.=0A> =0A> > So say I perform an operation like :=0A> > =
=0A> > =A0 UPDATE foo SET bar=3D'baz'=0A> > =0A> > are the following assump=
tions correct?=0A> > =0A> > - The first time this changed data hits the dis=
k, it is as an entry in the WAL log=0A> > =0A> > - At some point a checkpoi=
nt occurs, and the changed data is written to the actual data file from=0A>=
 > system memory (the "dirty data pages"?)=0A> > =0A> > - the only time the=
 actual data files will be updated from the WAL log (i.e. not from system m=
emory)=0A> > will be after a crash, when the logs are replayed from the las=
t checkpoint?=0A> =0A> All three are correct.=0A=0AMany thanks for the answ=
ers, its cleared things up for me :)=0A=0A- drew

pgsql-general by date:

Previous
From: Scott Marlowe
Date:
Subject: Re: REINDEX deadlock - Postgresql -9.1
Next
From: Anoop K
Date:
Subject: Re: REINDEX deadlock - Postgresql -9.1