I m trying to install Postgresql on ZORIN 3.0, an Ubuntu based distro running WINE 1.1.42. When I start setup, after language selection, it gives the error "Failed to create process: 2!".
Please guide me on how to solve this problem.
Postgresql 8.0 installation
-
Martin Gregorie
Postgresql 8.0 installation
On Mon, 2010-08-02 at 06:10 -0500, sabir_mustafa wrote:
- Is this Linux native PostgreSQL or are you trying to run it
under wine?
- If the latter, why aren't you running the native version?
- Why run a version as old as 8.0 when the current version for
Fedora 12 is 8.3.8?
Second: what's in the PostgreSQL log? It is in the directory where
you're running PostgreSQL and is called pg_log/postgresql-xxx.log where
'xxx' is the day of the week when the log was created, so my log today
is called pg_log/postgresql-Mon.log
Martin
Obvious first questions:I m trying to install Postgresql on ZORIN 3.0, an Ubuntu based distro running WINE 1.1.42. When I start setup, after language selection, it gives the error "Failed to create process: 2!".
Please guide me on how to solve this problem.
- Is this Linux native PostgreSQL or are you trying to run it
under wine?
- If the latter, why aren't you running the native version?
- Why run a version as old as 8.0 when the current version for
Fedora 12 is 8.3.8?
Second: what's in the PostgreSQL log? It is in the directory where
you're running PostgreSQL and is called pg_log/postgresql-xxx.log where
'xxx' is the day of the week when the log was created, so my log today
is called pg_log/postgresql-Mon.log
Martin
-
sabir_mustafa
- Newbie
- Posts: 3
- Joined: Sun Aug 01, 2010 1:33 pm
The PostgeSQL i am trying to run is a Windows Installer. The problem is that our old developed application is in PowerBuilder (I m still confirming version from the operators) with back end database PostgeSQL 8.
I want my people to get rid of silly viruses. Thats why I want to change the whole thing to Wine rather than having a new development.
I want my people to get rid of silly viruses. Thats why I want to change the whole thing to Wine rather than having a new development.
Don't rely on Wine for that. http://wiki.winehq.org/FAQ#head-3cb8f05 ... 4e305a0459sabir_mustafa wrote:I want my people to get rid of silly viruses.
-
Martin Gregorie
Postgresql 8.0 installation
On Mon, 2010-08-02 at 10:35 -0500, sabir_mustafa wrote:
There's really no reason for running PostgreSQL under Wine: PowerBuilder
doesn't care where the database is installed as long as it can open a
connection to it. In addition, there are a number of disadvantages:
- PostgreSQL may be more fragile run under Wine
- wine will demand access to an X-server while running PostgresQL
which means you probably can't run it as a background task
- there may be performance overheads that native PostgreSQL won't have
- you won't be able to run PostgreSQL as a Linux service.
IMO this is a major disadvantage because:
- running as a service means that PostgreSQL will automatically
start when the system is booted and will be correctly shut down
when Linux is stopped.
- Its easy to configure native PostgreSQL so it will just sit
quietly in the background and look after itself.
- you can set up automatically scheduled database backups
- PostgreSQL updates will be automatically applied by your distor's
package manager.
PostgreSQL will almost certainly be available as a standard package for
your distro, so it can be installed by your distro's package manager.
There is a full compliment of native, ODBC, JDBC and Python drivers
available for it too.
PostgreSQL for Linux can easily be addressed as localhost:5432 from Wine
if its installed on the same hardware as PowerBuilder.
notice any native support, so you'll probably have to use ODBC.
don't need to run the target database under wine as well: it can be run
under Linux on the same hardware or on a remote server - all that
matters is that PowerBuilder can see the database server.
As an example, I remember trouble shooting a database performance
problem back in the mid 90s: the PowerBuilder application was in London
on a PC but the target database was Sybase 9 on an NCR UNIX box in Abu
Dhabi. The problem turned out to be the auto-generated SQL SELECT
statement in the PowerBuilder application. We replaced it with a
hand-written query and got the performance we expected. I don't know if
PowerBuilder autogenerates better SQL these days, but its worth looking
at it to see if its sensible and to use the Postgres EXPLAIN verb to see
how costly the query is and optimise it/add supporting indexes etc. as
needed.
Martin
OK. I thought it might be.The PostgeSQL i am trying to run is a Windows Installer.
There's really no reason for running PostgreSQL under Wine: PowerBuilder
doesn't care where the database is installed as long as it can open a
connection to it. In addition, there are a number of disadvantages:
- PostgreSQL may be more fragile run under Wine
- wine will demand access to an X-server while running PostgresQL
which means you probably can't run it as a background task
- there may be performance overheads that native PostgreSQL won't have
- you won't be able to run PostgreSQL as a Linux service.
IMO this is a major disadvantage because:
- running as a service means that PostgreSQL will automatically
start when the system is booted and will be correctly shut down
when Linux is stopped.
- Its easy to configure native PostgreSQL so it will just sit
quietly in the background and look after itself.
- you can set up automatically scheduled database backups
- PostgreSQL updates will be automatically applied by your distor's
package manager.
PostgreSQL will almost certainly be available as a standard package for
your distro, so it can be installed by your distro's package manager.
There is a full compliment of native, ODBC, JDBC and Python drivers
available for it too.
PostgreSQL for Linux can easily be addressed as localhost:5432 from Wine
if its installed on the same hardware as PowerBuilder.
Do you know that PowerBuilder is compatible with PostgreSQL? I didn'tThe problem is that our old developed application is in PowerBuilder
(I m still confirming version from the operators) with back end
database PostgeSQL 8.
notice any native support, so you'll probably have to use ODBC.
Understood, but while PowerBuilder will have to be run under Wine youI want my people to get rid of silly viruses. Thats why I want to
change the whole thing to Wine rather than having a new development.
don't need to run the target database under wine as well: it can be run
under Linux on the same hardware or on a remote server - all that
matters is that PowerBuilder can see the database server.
As an example, I remember trouble shooting a database performance
problem back in the mid 90s: the PowerBuilder application was in London
on a PC but the target database was Sybase 9 on an NCR UNIX box in Abu
Dhabi. The problem turned out to be the auto-generated SQL SELECT
statement in the PowerBuilder application. We replaced it with a
hand-written query and got the performance we expected. I don't know if
PowerBuilder autogenerates better SQL these days, but its worth looking
at it to see if its sensible and to use the Postgres EXPLAIN verb to see
how costly the query is and optimise it/add supporting indexes etc. as
needed.
Martin
-
sabir_mustafa
- Newbie
- Posts: 3
- Joined: Sun Aug 01, 2010 1:33 pm
