Robert Haas <robertmh...@gmail.com> wrote:
> if the database has checkpointed
I haven't been exactly clear on the risks about which Tom and Robert
have been concerned; is it a question about whether we change the
meaning of these settings to something more complicated?:
checkpoint_segments (integer)
Maximum number of log file segments between automatic WAL
checkpoints
checkpoint_timeout (integer)
Maximum time between automatic WAL checkpoints
I can see possibly changing the latter when absolutely nothing has
been written to WAL since the last checkpoint, although I'm not sure
that should suppress flushing dirty pages (e.g., from hinting) to
disk. Such a change seems like it would be of pretty minimal
benefit, though, and not something for which it is worth taking on
any risk at all. Any other change to the semantics of these
settings seems ill advised on the face of it.
... or am I not grasping the issue properly?
-Kevin
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
