An interesting complement about the previous failing test:

Although I disabled the "flushing" feature...

  sh> grep flush_after xxx/postgresql.conf
  bgwriter_flush_after = 0                # 0 disables,
  backend_flush_after = 0         # 0 disables,
  wal_writer_flush_after = 0              # 0 disables
  checkpoint_flush_after = 0              # 0 disables,

the test still fails with "head":

  ERROR:  could not fsync file "base/16384/16397.1": No such file or directory
  ERROR:  checkpoint request failed
  HINT:  Consult recent messages in the server log for details.

So this seem to suggest that there is an underlying issue independent from the flushing file.


Sent via pgsql-hackers mailing list (
To make changes to your subscription:

Reply via email to