On Mon, 08 Sep 2003, Tom Lane wrote:
> Ben Grimm <[EMAIL PROTECTED]> writes:
> > On Thu, 04 Sep 2003, Tom Lane wrote:
> >> Ben Grimm <[EMAIL PROTECTED]> writes:
> >>> I haven't tried the 7.4 beta, so it may be fixed there - but in
> >>> 7.3.4, pg_dumpall doesn't output global database ACL's.
> >>
Hi,
A client is using postgresql 7.1.3, and to_date() and to_timestamp()
functions fail sometimes,However they never do in postgresql 7.3.2.
Are these bugs?
Thx
_
Help STOP SPAM with the new MSN 8 and get 2 months FREE*
http://jo
Added to TODO:
* Have pg_dump -c clear the database using dependency
information
---
Preston Landers wrote:
>
>
I spoted a trouble with the HEAD taged PG version CVS updated
on the 4th of september.
During a COPY FROM stdin query involving a VARCHAR[] column I
experienced troubles with values containing an escaped double quote.
The query was expressed like this on the application side:
"CO
On Thu, 04 Sep 2003, Tom Lane wrote:
> Ben Grimm <[EMAIL PROTECTED]> writes:
> > I haven't tried the 7.4 beta, so it may be fixed there - but in
> > 7.3.4, pg_dumpall doesn't output global database ACL's.
>
> This is fixed for 7.4.
Is there a patch to backport this to the 7.3 series? Without i
Hi Theodore
I download 7.3.4 and build it !!!
All of PostgreSQL successfully made. Ready to install.
i am in OS X.2.6 and
% gnumake -v
GNU Make version 3.79, by Richard Stallman and Roland McGrath.
Built for powerpc-apple-darwin6.0
Copyright (C) 1988, 89, 90, 91, 92, 93, 94, 95, 96, 97, 98, 99
Find it
gcc 3.3 dont support space character (0x20) before #ifdef
try this :
test.c
#include
int main()
{
return 0;
}
gcc -traditional-cpp -g -O2 -Wall -Wmissing-prototypes
-Wmissing-declarations -c -o
test.o test.c
you have the same errors ...
but this works
gcc -traditional-cpp -g -O
Bertrand Petit <[EMAIL PROTECTED]> writes:
> One of the attribs value is piped to the backend as {"3/4\""}, this is
> how the array appears on the wire, and PG rejected it with the
> following message, as submited to syslog:
> postgres[90257]: [51-1] ERROR: malformed array literal: "{"3/4""}"
Se
On Monday 08 September 2003 09:32, Marek Lewczuk wrote:
> Hello,
> I think that there is a bug in plPGSQL - or maybe I don't know something
> about this language. Try to create this function
[snip]
> And when i execute: SELECT test(NULL, 'buuu'); -> it returns me NULL
> value, when it should return
I had the same success using 7.3.2 with Cygwin:
e=# SELECT functest1('A','B'), functest1(null,'B'), functest2('A','B'),
functest2(null,'B');
functest1 | functest1 | functest2 | functest2
---+---+---+---
A | B | A | B
(1 row)
e=# select ve
Marek Lewczuk wrote:
Hello,
I think that there is a bug in plPGSQL - or maybe I don't know something
about this language. Try to create this function
Ok., this is the function created in plPGSQL:
CREATE FUNCTION "public"."test" (text, text) RETURNS text AS'
BEGIN
IF $1 THEN
RETURN $1;
ELSE
11 matches
Mail list logo
