Thread Info
  • State Suggested Answer
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 2 subscribers
  • Views 5947 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Linux Postgres Database excluded directories still being scanned

InternationalPossumBrotherhood

We have a linux database, running postgres, that has excluded directories configured but these 'excluded' directories are still being scanned. This is causing major performance issues, hence the reason the directory was excluded, has anyone else experienced issues like this?

Directories excluded:

/mnt/DATA2/pg

/mnt/DATA2/pgsql

What we're seeing in the logs:

talpa-deny: Error occurred while closing /mnt/DATA2/pgsql/data/cmp_tbs2/PG_9.1_201105231/16842/462530461 on behalf of process postgres[567/567] owned by 26(26)/26(26) <49>
talpa-deny: Error occurred while opening /mnt/DATA2/pgsql/data/cmp_tbs2/PG_9.1_201105231/16842/462530461 on behalf of process postgres[1176/1176] owned by 26(26)/26(26) <49>
talpa-cache: Disabled
talpa-cache: Enabled
runkbot[27866]: segfault at 0000000004000000 rip 00000031db07579e rsp 00007fff90e686f0 error 4


Thanks in advance for your help!


This thread was automatically locked due to age.
  • 0

    Hello InternationalPossumBrotherhood,

    I haven't tested it (Season's laziness) but Appendix chapter 17.2.1 in the configuration guide suggests you need a trailing slash (/mnt/DATA2/pgsql/) if you mean directory (and its subdirectories) - actually coherent 'cause you need a means to differentiate between a file and a directory.  

    Christian

Unfiltered HTML