| From: | Magnus Hagander <magnus(at)hagander(dot)net> |
|---|---|
| To: | Peter Geoghegan <peter(dot)geoghegan86(at)gmail(dot)com> |
| Cc: | Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>, jd <jd(at)commandprompt(dot)com>, pgeu-general <pgeu-general(at)postgresql(dot)org> |
| Subject: | Re: "could not stat file "base/17436/119145": Permission denied" when performing pg_database_size() on windows with 8.4.0 |
| Date: | 2010-01-31 16:20:29 |
| Message-ID: | 9837222c1001310820u4c05a6ccn9aff1d7d3ceb129c@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgeu-general |
On Sun, Jan 31, 2010 at 17:05, Peter Geoghegan
<peter(dot)geoghegan86(at)gmail(dot)com> wrote:
> Hi Stefan,
>
>> that is usually caused by missbehaving antovirussoftware that tries to do
>> "on-access" scanning. Try excluding PGDATA from whatever you have there - or
>> even better deinstall...
>
> It may well be misbehaving anti-virus software (this machine is not a
> dedicated database server). I've added an exclusion rule to PGDATA.
Please note that it is quite often not enough to just add the
exclusion - you may need to uninstall it.
That said, starting with an exclusion is a good thing. Which is not
pg-specific at all - I un-fondly recall two instances of antirivus
deciding it knows how to clean a virus out of a SQL Server database
file.. Yeah, fun was ensured...
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2010-01-31 17:16:13 | Re: "could not stat file "base/17436/119145": Permission denied" when performing pg_database_size() on windows with 8.4.0 |
| Previous Message | Peter Geoghegan | 2010-01-31 16:05:45 | Re: "could not stat file "base/17436/119145": Permission denied" when performing pg_database_size() on windows with 8.4.0 |