View Single Post

   
  #2 (permalink)  
Old 04-15-2008, 09:46 PM
Tom Lane
 
Posts: n/a
Default Re: Checkpoints and buffers that are hint-bit-dirty

Gregory Stark <stark@enterprisedb.com> writes:
> When we checkpoint we write out all dirty buffers. But ISTM we don't really
> need to write out buffers which are dirty but which have an LSN older than the
> previous checkpoint. Those represent buffers which were dirtied by a
> non-wal-logged modification, ie, hint bit setting. The other non-wal-logged
> operations will sync the buffer themselves when they're done.


In the current dispensation we don't really care how long a checkpoint
takes, so I don't see the advantage to be gained.

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match

Reply With Quote