2010/7/8 el dorado <do_ra_do@mail.ru>:
> Thank you for your answers.
> Well, the beginning of the story in details is here
(http://archives.postgresql.org/pgsql-general/2010-06/msg01135.php).Shortly, I tried to use functions from my own dll,
butgot an error "Could not open relation base\16123\16222: No such file or directory". Later I found out, using
'ProcessMonitor', that for some reason process 'postgres.exe' looked for this relation not in
'C:\PostgreSQL\8.4\data\base\16123\16222'but in 'C:\Users\postgres\AppData\Roaming\MyApplicationName\base\16123\16222'
-certainly, there is no such file.
>
>
>> Did you check, that registry key "Data Directory" is set properly in
>> "HKEY_LOCAL_MACHINE\SOFTWARE\PostgreSQL\Installations\postgresql-8.4"
>> folder?
> Usually I don't use standard Windows Installer but take binaries. So there is no such branch in registry. When I
triedto make test and install it from Installer I got the same result. :( "Data Directory" was set to PG-specific
applicationdir.
So this is an issue with an extension of your own? Can you post the code?
You'll have to excuse us being skeptical about PostgreSQL being
fundamentally broken in the way you describe. The Windows installer
alone is downloaded tens of thousands of times per week, so I'm pretty
sure someone would have reported such an issue before now. And that's
ignoring the vast amount of testing that goes into every release,
including on 32 and 64 bit versions of XP through 7 and 2003 through
2008R2.
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise Postgres Company