[BUGS] Installation fails for postgresql-8.0.0-beta4 on WindowsXP SP1

[Mehul Doshi-A20614]

Hi,

I am trying to install the 8.0 beta4 version for Windows onto my system and 
facing an error which I can't fix.

System: Windows XP, Sevice Pack 1

I am an admin on my system, but a regular user on a domain. I have created a 
non-admin user named "postgres" which is a member of the "Users" group 
(Restricted Users).

I have run the entire installation in exactly the same way as is given 
http://pginstaller.projects.postgresql.org/ 

However, this is the error message that I get.

Error Pop-up message:
"Failed to run initdb: 1! Please see the logfile in "C:\Program 
Files\PostgreSQL\8.0.0-beta4\tmp\initdb.log"
Note! You must read/copy this logifle before you click OK, or it will be 
automatically removed."


Please find the log (initdb.log) below
---The
 files belonging to this database system will be owned by user "postgres".
This user must also own the server process.

The database cluster will be initialized with locale C.

fixing permissions on existing directory C:/Program 
Files/PostgreSQL/8.0.0-beta4/data ... ok
creating directory C:/Program Files/PostgreSQL/8.0.0-beta4/data/global ... ok
creating directory C:/Program Files/PostgreSQL/8.0.0-beta4/data/pg_xlog ... ok
creating directory C:/Program 
Files/PostgreSQL/8.0.0-beta4/data/pg_xlog/archive_status ... ok
creating directory C:/Program Files/PostgreSQL/8.0.0-beta4/data/pg_clog ... ok
creating directory C:/Program Files/PostgreSQL/8.0.0-beta4/data/pg_subtrans ... 
ok
creating directory C:/Program Files/PostgreSQL/8.0.0-beta4/data/base ... ok
creating directory C:/Program Files/PostgreSQL/8.0.0-beta4/data/base/1 ... ok
creating directory C:/Program Files/PostgreSQL/8.0.0-beta4/data/pg_tblspc ... ok
selecting default max_connections ... 10
selecting default shared_buffers ... 50
creating configuration files ... ok
creating template1 database in C:/Program 
Files/PostgreSQL/8.0.0-beta4/data/base/1 ... Execution of PostgreSQL by a user 
with administrative permissions is not permitted.
The server must be started under an unprivileged user ID to prevent
possible system security compromises.  See the documentation for
more information on how to properly start the server.
child process was terminated by signal 1
initdb: failed
initdb: removing contents of data directory "C:/Program 
Files/PostgreSQL/8.0.0-beta4/data"

---

It somehow recognizes the account as an admin, when it is definitely not. Just 
to check, I even tried with the admin account itself and it kicked me off right 
in Step 4 of the procedure. So if it goes past Step 4 it already recognizes 
that it is not admin account.

I think this issue has been raised before 
http://pgfoundry.org/tracker/index.php?func=detail&aid=188&group_id=107&atid=126

Please let me know if there is something that needs to be fixed by me before 
this installation goes through successfully.

Regards,
Mehul

---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])

[BUGS] interval conversion bug

[Andrzej Wojtaszek]

Hi,
 
I'm afraid that operator ::interval not working propertly 
example:
 
select 1
##
select now() + (1||' day')::interval;
working propertly
##

I have my function writen in plpgsql

function test(varchar) returns varchar; 

select 2
##
select my_name,
  test('12')
from table1
##

returns 'aaa', '12 MONTH' 

working  propertly

select 3
##
select my_name 
 now() +  (test('12'))::interval
from table1
##

not working with error "cannot cast type character varying to iterval"



Facts 
Database version 7.4.5
psql version 7.4.5
platform PIV
linux : Debian

Regards

Andrzej Wojtaszek




---(end of broadcast)---
TIP 9: the planner will ignore your desire to choose an index scan if your
  joining column's datatypes do not match

Re: [BUGS] interval conversion bug

[Tom Lane]

"Andrzej Wojtaszek" <[EMAIL PROTECTED]> writes:
> not working with error "cannot cast type character varying to iterval"

8.0 is more flexible about that, but for the moment use type text
instead of varchar.

regards, tom lane

---(end of broadcast)---
TIP 8: explain analyze is your friend

Re: [BUGS] interval conversion bug

[Stephan Szabo]

On Thu, 25 Nov 2004, Andrzej Wojtaszek wrote:

> I'm afraid that operator ::interval not working propertly
> example:
>
> select 1
> ##
> select now() + (1||' day')::interval;
> working propertly
> ##

This is a text -> interval conversion

> select 3
> ##
> select my_name
>  now() +  (test('12'))::interval
> from table1
> ##

This is a varchar -> interval conversion.

It looks like 7.4 doesn't have the latter conversion and requires you to
go through text to make the conversion. 8.0 appears to add direct
conversions from varchar.

---(end of broadcast)---
TIP 8: explain analyze is your friend