So here is a strange question.
I am using PostgreSQL 9.4.0 (Yes, I know 9.4.9 is most recent but it's out of my control)
O/S is AWS Debian 3.16.7-2 (2014-11-06) x86_64 GNU/Linux.
I list the creation time for a WAL file and it shows:
/home/mdavidson/dba$ ls -l --time=ctime /d-log/pg_xlog/000000010000000D000000C9
-rw------- 1 postgres postgres 16777216 Sep 29 07:14 /d-log/pg_xlog/000000010000000D000000C9
but then I list the access time for a WAL file and it shows:
/home/mdavidson/dba$ ls -l --time=atime /d-log/pg_xlog/000000010000000D000000C9
-rw------- 1 postgres postgres 16777216 Sep 7 14:33 /d-log/pg_xlog/000000010000000D000000C9
How is it possible for the WAL file to be accessed BEFORE it was created?
Am I overlooking something simple?
I am using PostgreSQL 9.4.0 (Yes, I know 9.4.9 is most recent but it's out of my control)
O/S is AWS Debian 3.16.7-2 (2014-11-06) x86_64 GNU/Linux.
I list the creation time for a WAL file and it shows:
/home/mdavidson/dba$ ls -l --time=ctime /d-log/pg_xlog/000000010000000D000000C9
-rw------- 1 postgres postgres 16777216 Sep 29 07:14 /d-log/pg_xlog/000000010000000D000000C9
but then I list the access time for a WAL file and it shows:
/home/mdavidson/dba$ ls -l --time=atime /d-log/pg_xlog/000000010000000D000000C9
-rw------- 1 postgres postgres 16777216 Sep 7 14:33 /d-log/pg_xlog/000000010000000D000000C9
How is it possible for the WAL file to be accessed BEFORE it was created?
Am I overlooking something simple?
Melvin Davidson
