pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
bgwriter update question
3+ messages / 2 participants
[nested] [flat]

* bgwriter update question
@ 2007-10-22 17:52 Mark Steben <msteben@autorevenue.com>
  2007-10-22 18:17 ` Re: bgwriter update question Tom Lane <tgl@sss.pgh.pa.us>
  0 siblings, 1 reply; 3+ messages in thread

From: Mark Steben @ 2007-10-22 17:52 UTC (permalink / raw)
  To: pgsql-admin

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?

 

Thanks for your time

 

Mark Steben

Senior Database Administrator
@utoRevenueT 
A Dominion Enterprises Company
480 Pleasant Street
Suite B200
Lee, MA 01238
413-243-4800 Home Office 
413-243-4809 Corporate Fax

msteben <blocked::mailto:name@autorevenue.com> @autorevenue.com

Visit our new website at 
 <blocked::http://www.autorevenue.com/; www.autorevenue.com

 

IMPORTANT: The information contained in this e-mail message is confidential
and is intended only for the named addressee(s). If the reader of this
e-mail message is not the intended recipient (or the individual responsible
for the delivery of this e-mail message to the intended recipient), please
be advised that any re-use, dissemination, distribution or copying of this
e-mail message is prohibited.  If you have received this e-mail message in
error, please reply to the sender that you have received this e-mail message
in error and then delete it.  Thank you.

 

^ permalink  raw  reply  [nested|flat] 3+ messages in thread

* Re: bgwriter update question
  2007-10-22 17:52 bgwriter update question Mark Steben <msteben@autorevenue.com>
@ 2007-10-22 18:17 ` Tom Lane <tgl@sss.pgh.pa.us>
  2007-10-22 18:30   ` Re: bgwriter update question Mark Steben <msteben@autorevenue.com>
  0 siblings, 1 reply; 3+ messages in thread

From: Tom Lane @ 2007-10-22 18:17 UTC (permalink / raw)
  To: Mark Steben <msteben@autorevenue.com>; +Cc: pgsql-admin

"Mark Steben" <msteben@autorevenue.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



^ permalink  raw  reply  [nested|flat] 3+ messages in thread

* Re: bgwriter update question
  2007-10-22 17:52 bgwriter update question Mark Steben <msteben@autorevenue.com>
  2007-10-22 18:17 ` Re: bgwriter update question Tom Lane <tgl@sss.pgh.pa.us>
@ 2007-10-22 18:30   ` Mark Steben <msteben@autorevenue.com>
  0 siblings, 0 replies; 3+ messages in thread

From: Mark Steben @ 2007-10-22 18:30 UTC (permalink / raw)
  To: 'Tom Lane' <tgl@sss.pgh.pa.us>; +Cc: pgsql-admin

Thanks Tom, every piece of new information adds to my education.
I'm going to put to bed this effort of trying to verify BGWRITER, 
knowing that it works in 8.2 and move on.

Regards,
Mark Steben

-----Original Message-----
From: Tom Lane [mailto:tgl@sss.pgh.pa.us] 
Sent: Monday, October 22, 2007 2:18 PM
To: Mark Steben
Cc: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] bgwriter update question 

"Mark Steben" <msteben@autorevenue.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




^ permalink  raw  reply  [nested|flat] 3+ messages in thread


end of thread, other threads:[~2007-10-22 18:30 UTC | newest]

Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2007-10-22 17:52 bgwriter update question Mark Steben <msteben@autorevenue.com>
2007-10-22 18:17 ` Tom Lane <tgl@sss.pgh.pa.us>
2007-10-22 18:30   ` Mark Steben <msteben@autorevenue.com>

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox