BUG #5653: Error reading the C:/Program Files/PostgreSQL/8.4/data/postgresql.conf"
The following bug has been logged online:
Bug reference: 5653
Logged by: Kesavan
Email address: kesavan@emmeskay.com
PostgreSQL version: 8.4.0-1
Operating system: Windows
Description: Error reading the C:/Program
Files/PostgreSQL/8.4/data/postgresql.conf"
Details:
This issue related to Bug #5253.
While Installing Postgres, Warning message thrown as
"Problem running post-install step. Installation may not complete
correctly.
Error reading the C:/Program Files/PostgreSQL/8.4/data/postgresql.conf"
If I proceed the installation it turns out the data directory is completely
empty. During the install, I did_not_ un-check the box asking if I wanted
to "Install pl/pgsql in template1 database", so it should have been in there
as well.
I ran the installer while logged into the Administrator account. So
absolutely no issue of Read/write access in "C:/Program
Files/PostgreSQL/8.4/data/postgresql.conf" file.
After few attempts, I was able to install without any issue in the same
system with same user and the same directory path.
So I want to know, what are the root causes for this issue. How to prevent
this issue? Also if the issue happens, is there any manual procedure to
populate the data (dictionary) folder?
On 09/12/10 8:23 AM, Kesavan wrote:
PostgreSQL version: 8.4.0-1
Operating system: Windows
8.4.0? thats rather old.... 8.4.4 is the current build of the 8.4
family, and the bug fixes listed in the release notes for each of the
interrim versions (8.4.1, .2, .3, .4) are fairly long.
and, "Windows" ? that describes a family of a dozen or more operating
systems, maybe more if you consider the home vs professional variants,
desktop vs server, and 32 vs 64 bit, etc etc.
On Sun, Sep 12, 2010 at 7:32 PM, John R Pierce <pierce@hogranch.com> wrote:
On 09/12/10 8:23 AM, Kesavan wrote:
PostgreSQL version: 8.4.0-1
Operating system: Windows8.4.0? thats rather old.... 8.4.4 is the current build of the 8.4 family,
and the bug fixes listed in the release notes for each of the interrim
versions (8.4.1, .2, .3, .4) are fairly long.
Yeah - the installer has also had numerous bug fixes since then; at
least some of which address many of the common causes of this
particular error.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise Postgres Company
Hi
OS : Windows XP Professional SP3.
Due to some of our product limitation, right now we can't migrate to
8.4.4. Hence we have to stick to 8.4.0-1.
Kindly provide me the root causes of this issue so that I can avoid
those pitfalls. Also if the issue comes, is there any script to complete
the installation manually.
Thanks in advance.
Regards
S.Kesavan
Show quoted text
On 9/13/2010 12:15 AM, Dave Page wrote:
On Sun, Sep 12, 2010 at 7:32 PM, John R Pierce <pierce@hogranch.com> wrote:
On 09/12/10 8:23 AM, Kesavan wrote:
PostgreSQL version: 8.4.0-1
Operating system: Windows8.4.0? thats rather old.... 8.4.4 is the current build of the 8.4 family,
and the bug fixes listed in the release notes for each of the interrim
versions (8.4.1, .2, .3, .4) are fairly long.Yeah - the installer has also had numerous bug fixes since then; at
least some of which address many of the common causes of this
particular error.
On Mon, Sep 13, 2010 at 4:48 AM, Kesavan <kesavan@emmeskay.com> wrote:
Hi
OS : Windows XP Professional SP3.
Due to some of our product limitation, right now we can't migrate to
8.4.4. Hence we have to stick to 8.4.0-1.Kindly provide me the root causes of this issue so that I can avoid
those pitfalls. Also if the issue comes, is there any script to complete
the installation manually.
I don't recall all of the root causes - but suffice it to say that
some of them are not necessarily feasible to work around anyway.
There are numerous other fixes in 8.4.4, which is 100% compatible with
8.4.0 (we have a strict bug-fix only policy for minor releases, unlike
some other DBMSs). There really is no good reason to not use the newer
version, especially as you haven't installed yet.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise Postgres Company
On 13/09/10 17:10, Dave Page wrote:
On Mon, Sep 13, 2010 at 4:48 AM, Kesavan <kesavan@emmeskay.com> wrote:
Hi
OS : Windows XP Professional SP3.
Due to some of our product limitation, right now we can't migrate to
8.4.4. Hence we have to stick to 8.4.0-1.Kindly provide me the root causes of this issue so that I can avoid
those pitfalls. Also if the issue comes, is there any script to complete
the installation manually.I don't recall all of the root causes - but suffice it to say that
some of them are not necessarily feasible to work around anyway.There are numerous other fixes in 8.4.4, which is 100% compatible with
8.4.0 (we have a strict bug-fix only policy for minor releases, unlike
some other DBMSs). There really is no good reason to not use the newer
version, especially as you haven't installed yet.
I've added a FAQ entry for this, as we've had more people with odd ideas
about updates lately. It needs a shorter title ;-) but otherwise should
cover things.
As usual, check/editing appreciated.
--
Craig Ringer
Tech-related writing: http://soapyfrogs.blogspot.com/
On Mon, Sep 13, 2010 at 11:12 AM, Craig Ringer
<craig@postnewspapers.com.au> wrote:
On 13/09/10 17:10, Dave Page wrote:
On Mon, Sep 13, 2010 at 4:48 AM, Kesavan <kesavan@emmeskay.com> wrote:
Hi
OS : Windows XP Professional SP3.
Due to some of our product limitation, right now we can't migrate to
8.4.4. Hence we have to stick to 8.4.0-1.Kindly provide me the root causes of this issue so that I can avoid
those pitfalls. Also if the issue comes, is there any script to complete
the installation manually.I don't recall all of the root causes - but suffice it to say that
some of them are not necessarily feasible to work around anyway.There are numerous other fixes in 8.4.4, which is 100% compatible with
8.4.0 (we have a strict bug-fix only policy for minor releases, unlike
some other DBMSs). There really is no good reason to not use the newer
version, especially as you haven't installed yet.I've added a FAQ entry for this, as we've had more people with odd ideas
about updates lately. It needs a shorter title ;-) but otherwise should
cover things.As usual, check/editing appreciated.
Thanks Craig. I wonder if it's worth mentioning that patching your own
build will also take more time/effort, and will require the same
amount of downtime as a normal upgrade.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise Postgres Company
Craig:
I've added a FAQ entry for this, as we've had more people with odd ideas
about updates lately. It needs a shorter title ;-) but otherwise should
cover things.As usual, check/editing appreciated.
I wanna suggest to have some words other DB-Vendors use for what is
similiar to our ..x releases; as in
equivalent to what O and MS calls "patchset", and I calls "WarpLevel",
and My calls "whatever"; way less intrusive then what MS calls
"ServicePacks"
Is somebody fluent enough in O/MS/I-speak to know those words?
Harald
--
GHUM Harald Massa
persuadere et programmare
Harald Armin Massa
Spielberger Straße 49
70435 Stuttgart
0173/9409607
no fx, no carrier pigeon
-
Using PostgreSQL is mostly about sleeping well at night.