Hello,
We have been using postgres 8.0.0beta4 successfully on various windows
machines for a while now, but we have run across a particular windows
machine of one of our customers where initdb.exe is failing with an exit
code of 1 for no reason that I can determine. The machine is running
windows
"Steve McWilliams" <[EMAIL PROTECTED]> writes:
> We have been using postgres 8.0.0beta4 successfully on various windows
> machines for a while now, but we have run across a particular windows
> machine of one of our customers where initdb.exe is failing with an exit
> code of 1 for no reason that I
Nevermind, I found out what this was. Turned out that the customer
machine in question had particularly heavy security settings and so the
enetaware account did not have permission to write into the directory
where it was trying to create PGDATA. Once I widened the settings on the
parent director
"Steve McWilliams" <[EMAIL PROTECTED]> writes:
> Nevermind, I found out what this was. Turned out that the customer
> machine in question had particularly heavy security settings and so the
> enetaware account did not have permission to write into the directory
> where it was trying to create PGDA
--- This script will demonstrate a bug-like misbehaviour found in the query
planner
--- of postgresql 8.0.0.rc3 server.
--- Run it as an user with administrative rights with psql
--- query planner behaviour as demonstrated:
--
--- Adding a constant expression c
=?ISO-8859-15?Q?J=F6rg_Hoppe?= <[EMAIL PROTECTED]> writes:
> --- SELECTing expressions, which do not access any table data,
> --- should not influence the execution plan.
Unfortunately, that assertion is dead wrong.
> SELECT R.a_ID, R.b_ID, v.constcol
>FROM t_b R LEFT JOIN v_test_bad V on R.
