The following bug has been logged online:
Bug reference: 1368
Logged by: Michiel Tas
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0
Operating system: W XP Home
Description:initdb fails
Details:
I am using FAQ_CYGWIN.txt but when I follow all instructions p
Hi! I've been using the
PostgreSQL database in Windows since the Beta2-dev3, and it had a bug I didn't
report. I've just downloaded the rc2, and uninstalled my previous version,
and installed the newest one, and it still have the same bug.
When executing the command
line functions psql, pg
The following bug has been logged online:
Bug reference: 1370
Logged by: David Bowen
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0
Operating system: Fedora Core 2/Athlon 950 processor
Description:Problem with arrays in PL/PGSQL
Details:
PostgreSQL 8.0.0rc
The rule-system seems to evaluate a functional value
of a column anew. Please confim if this is a
documented/intentional behaviour of the rule system?
The order of evaluation of the expresion(s) within
original statemant and rule differ between "on insert"
and "on update" rules.
For details see
Sorry, I forgot to say that functions output
that string, but the function executes perfectly.
For example:
createdb -U kuaimare dbkuaima
could not find a "createdb" to
execute
Password:
CREATE DATABASE
And the database (or the query, or the data
dump, etc.) executes perfectly, but with t
Hi
I'm using tsearch2 since postgresql-7.4.0 without problems with UTF-8
(yes i know about tolower() problems in postgresql < 8).
I tried postgresql-8.0beta and rc (up to rc3) and all versions contains
bug in tsearch2. (probably in ispell code part)
I can set up tsearch without problems for unicode
jan pfaler <[EMAIL PROTECTED]> writes:
> The rule-system seems to evaluate a functional value
> of a column anew. Please confim if this is a
> documented/intentional behaviour of the rule system?
Yes.
> The order of evaluation of the expresion(s) within
> original statemant and rule differ betwe
On Mon, Jan 03, 2005 at 03:11:05AM +, David Bowen wrote:
> test=# select crosstab(1);
> ERROR: array value must start with "{" or dimension information
> CONTEXT: PL/pgSQL function "crosstab" line 5 at block variables
> initialization
> $ cat /home1/dmb/crosstab
> CREATE OR REPLACE FUNCTION
Did we ever find the solution to this, or did anyone find the cause?
---
T.J. wrote:
> Having some problems (still, hehe) getting SSL to work properly on
> windows in the new 8.0 (all vers) environment (where cert/key is re
Thanks Tom,
Refering to your answer: The syntax "NEW.column" seems
to hint rather to "the new value" of column as opposed
to "the expression for the new value", c.f.
"OLD.column". The fact that the order of evaluation
changes underlines the inconsistency; the order of
evaluation would not matter
Yeah, I redownloaded and tried again with no problems...weird...sorry
for the false positive ;)
Magnus Hagander wrote:
I just rebuilt RC3 from scratch without any problems on MingW. I don't
see any problems.
The paths it's complaining about should be in
src/port/pg_config_paths.h, and this file s
Not to my knowledge. By the way, for future reference on windows it
looks for the cert/key in the linux equivalent of
`pwd`/.postgresql/postgresql.crt/key, instead of
$HOME/.postgresql/postgresql.crt/key. Maybe you already knew this but I
had to do testing to figure it out so hopefully that bit
"T.J." <[EMAIL PROTECTED]> writes:
> Not to my knowledge. By the way, for future reference on windows it
> looks for the cert/key in the linux equivalent of
> `pwd`/.postgresql/postgresql.crt/key, instead of
> $HOME/.postgresql/postgresql.crt/key.
Actually, it asks getpwuid() for the user's hom
13 matches
Mail list logo