Skip site navigation (1) Skip section navigation (2)

Re: bgwriter update question

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Mark Steben" <msteben(at)autorevenue(dot)com>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: bgwriter update question
Date: 2007-10-22 18:17:32
Message-ID: 19802.1193077052@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-admin
"Mark Steben" <msteben(at)autorevenue(dot)com> writes:
> I'm running on 7.4.5 (pre bgwriter) and moving to 8.2 in 3 weeks. I turn
> fsync off on my testing server. When I update a table I expect the file in
> the base directory to remain the same size until the next syncpoint when it
> would then update. But it increases immediately. I thought updates remain in
> memory until syncpoint in pre-8.0. Am I missing somethng?

The updates don't go to disk immediately (they didn't in 7.4 either).
But we always allocate disk space immediately when needed, to make sure
it's available.  Otherwise we could face the embarrassing situation of
having noplace to put rows inserted by an already-reported-committed
transaction.

			regards, tom lane

In response to

Responses

pgsql-admin by date

Next:From: Mark StebenDate: 2007-10-22 18:30:35
Subject: Re: bgwriter update question
Previous:From: Mark StebenDate: 2007-10-22 17:52:30
Subject: bgwriter update question

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group