The following bug has been logged online:
Bug reference: 1389
Logged by: Gustav Lindenberg
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0.0rc2
Operating system: Red Hat Enterprise Linux ES release 3 (Taroon Update 3)
Description:2 x 3.1 Gz Intel Cpu, 4Gb RAM
If PostgreSQL is intalled with native language support with the windows
installer and
if German is used as locale, local characters like Umlaute are displayed
wrong in the windows command window. In PG-Admin's Helpfile, which is
from beta5, but no longer in the documentation of version rc3 and r
1. Python as PL was greyed out an could not be installed again via the
installer - contrary to rc3, where PL/Python's installation was offered
and did work.
2. When trying to install plpythonu with creatlang, this was not
possible because of something like "error in python.dll: python23.dll
n
The default file and directory-rights set by postgesql for the data
directory are such, that anybody has the right to read, write and delete
files.
The installer as well as initdb should set reasonable rights or the user
should at least be warned that he should adjust the file and directory
ri
I wanted to install rc4 on Windows XP in g:\pgsql and selected this in
the Installprocess.
PGDATA was already set to this directory.
However, PostgeSQL as well as the data-directory were installed at
C:\Programme\PostgreSQL\8.0.0-rc4
resp.
C:\Programme\PostgreSQL\8.0.0-rc4\data
Initdb and pg_ctl s
I tryed to load a database dumped from version 7.4.3 which has a
function written in plpython.
The process seems to freeze at a "Create function" when I used psql and
the text-version of the dump.
After installing plpythonu it works.
psql should print an error-message indicting that plpython (or
Removed cc to pgsql-patches since that's not the list for this.
John Hansen wrote:
It seems rules don't work as expected.
I could be wrong,... In which case, what am I doing wrong?
A rule is like a macro, rewriting the query plan. You're trying to use
it as though it is a trigger. The side-effects
This permission is inherited from your Program Files folder, if you
install in the default location. If you install with the data on a
separate partition (which would be recommended for any larger
installation), it's inherited from whatever the parent permissions are
there.
Might be worthwhile t
> If PostgreSQL is intalled with native language support with
> the windows installer and if German is used as locale, local
> characters like Umlaute are displayed wrong in the windows
> command window. In PG-Admin's Helpfile, which is from beta5,
> but no longer in the documentation of versio
> 1. Python as PL was greyed out an could not be installed
> again via the installer - contrary to rc3, where PL/Python's
> installation was offered and did work.
This means that you don't have python23.dll on your system.
> 2. When trying to install plpythonu with creatlang, this was
> not
> I wanted to install rc4 on Windows XP in g:\pgsql and
> selected this in the Installprocess.
> PGDATA was already set to this directory.
> However, PostgeSQL as well as the data-directory were installed at
> C:\Programme\PostgreSQL\8.0.0-rc4
> resp.
> C:\Programme\PostgreSQL\8.0.0-rc4\data
> Ini
Right, except:
create table test (a text, b int);
create or replace rule test_rule as on insert to test where exists(select 1
from test where a = NEW.a) do instead select * from test;
insert into test (a,b) VALUES ('first',2);
a | b
---+---
first | 2
(1 row)
select * from test;
a
Hi,
I try a "make check" without success.
The compilation is done correctly.
But "make check" throws:
== creating temporary installation==
== initializing database system ==
== starting postmaster=
John Hansen wrote:
Right, except:
create table test (a text, b int); create or replace rule test_rule
as on insert to test where exists(select 1 from test where a = NEW.a)
do instead select * from test;
insert into test (a,b) VALUES ('first',2); a | b ---+--- first
| 2 (1 row)
select * from t
Pailloncy Jean-Gerard <[EMAIL PROTECTED]> writes:
> # cat src/test/regress/log/postmaster.log
>> WARNING: could not create Unix-domain socket
Hmm. That's pretty odd --- the warning indicates that
StreamServerPort() failed to open a local socket, but all of the
expected failure paths will log an
Pailloncy Jean-Gerard <[EMAIL PROTECTED]> writes:
The only code path I see offhand in which no message would be logged
is if the ListenSocket[] array is already full. Is it possible that
you have 10 or more IP addresses that "localhost" would bind to?
>>
>>> 2 IPs + 3 alias on 2 in
Pailloncy Jean-Gerard <[EMAIL PROTECTED]> writes:
> ===
> 8 of 96 tests failed.
> ===
The failures all seem to be due to individual tests not getting run:
> ! psql: could not fork new process for connection: Resource temporarily
> unavailable
> ! psql: cou
System is Windows XP, the postgres-installer (postgresql-8.0.0-rc5.zip
resp. .msi) was used to install
envirement variable PGDATA is set to g:\pgsql
Never before (7.x versions, older version 8 beta/rc) I have got the
following response/problem with an initdb:
C:\Programme\PostgreSQL\8.0.0-rc5\b
The installer will override any environment variables, as it executes
with its own environment in Windows Installer. To change a directory,
use the installer features for it. See the FAQ question 3.6.
I did that, and here is FAQ 3.6:
I changed the directory but PostgreSQL was still installed in the
OS ist Windows XP Prof, PgSQL version is rc5 via windowsinstaller
When trying to restore a db, psql does not ask for the password but
responds imediately with an erromessage as in the following example:
F:\doka\bak>psql -U postgres template1 < pg_dump_all_2005-01-11.txt
Password:
psql: FATAL: pa
Magnus Hagander wrote:
This information is still in the documentation, it has moved to a
different location. It's in the docmentation for the psql tool now.
(It's under Client Application)
Yes it is, but the message in the source code has not been changed,
which is very misleading,
as you can see
Christoph Becker wrote:
OS ist Windows XP Prof, PgSQL version is rc5 via windowsinstaller
When trying to restore a db, psql does not ask for the password but
responds imediately with an erromessage as in the following example:
F:\doka\bak>psql -U postgres template1 < pg_dump_all_2005-01-11.txt
Pa
Christoph Becker <[EMAIL PROTECTED]> writes:
> OS ist Windows XP Prof, PgSQL version is rc5 via windowsinstaller
> When trying to restore a db, psql does not ask for the password but
> responds imediately with an erromessage as in the following example:
> F:\doka\bak>psql -U postgres template1 <
23 matches
Mail list logo
