Re: [BUGS] [pgsql-bugs] pg_dumpall (7.3) 'public' schema bug

2004-11-17 Thread Bruno Wolff III
On Wed, Nov 17, 2004 at 11:53:10 -0800, Josh Berkus <[EMAIL PROTECTED]> wrote: > Karl, > > > I don't care that much about the behavior, it's easy enough > > to delete 'public'.  I do think that a note should be > > made in the administrator manual regards system upgrades > > where pg_dump(all) s

Re: [BUGS] [COMMITTERS] pgsql: Remove ill-considered suppression of gcc warnings in plperl, and

2004-11-17 Thread Michael Fuhr
On Wed, Nov 17, 2004 at 08:34:37PM -0500, Tom Lane wrote: > BTW, on my machine your test case does NOT fail if you declare the > function as plperlu instead of plperl. Same for you? Yep: with plperlu I don't get the crash, neither on FreeBSD nor on Solaris, at least not for arrays with up to one

Re: [BUGS] [COMMITTERS] pgsql: Remove ill-considered suppression of gcc warnings in plperl, and

2004-11-17 Thread Tom Lane
Michael Fuhr <[EMAIL PROTECTED]> writes: > On Wed, Nov 17, 2004 at 09:23:37PM +, Tom Lane wrote: >> Remove ill-considered suppression of gcc warnings in plperl, and fix >> some of the bugs exposed thereby. > These changes may not have targeted the problem mentioned in the > "plperl crashes bac

Re: [BUGS] [HACKERS] split_part bug

2004-11-17 Thread Tom Lane
John Hansen <[EMAIL PROTECTED]> writes: >> Works fine for me. What encoding/locale are you using? > unicode / c [ shrug... ] Works fine for me in unicode, too. u=# select split_part('a b c d e f g h i j k l m n o p q r s t u v w x y z',' ',1); split_part a (1 row) u=# select s

Re: [BUGS] [HACKERS] split_part bug

2004-11-17 Thread Tom Lane
John Hansen <[EMAIL PROTECTED]> writes: > PostgreSQL 8.0b4 as released. > select split_part('a b c d e f g h i j k l m n o p q r s t u v w x y > z',' ',1); > select split_part('a b c d e f g h i j k l m n o p q r s t u v w x y > z',' ',2); > select split_part('a b c d e f g h i j k l m n o p q r s

Re: [BUGS] [pgsql-bugs] pg_dumpall (7.3) 'public' schema bug

2004-11-17 Thread Josh Berkus
Karl, > I don't care that much about the behavior, it's easy enough > to delete 'public'. ÂI do think that a note should be > made in the administrator manual regards system upgrades > where pg_dump(all) scripts are given if this is going to be > the behavior. This isn't isolated to the "public"

[BUGS] a question about the installation

2004-11-17 Thread Josh Berkus
P: > Â I encounter some error while trying to build postgresql-8.0.0beta4. > Â When I run gmake, it reports that some macros used in path.c are not > defined. I check that file and find that macros such as PGBINDIR are really > not defined. Please tell me what should I do now. Um, did you run con

Re: [BUGS] BUG #1324: create domain strange behaviour

2004-11-17 Thread Tom Lane
"PostgreSQL Bugs List" <[EMAIL PROTECTED]> writes: > Description:create domain strange behaviour IIRC, plpgsql is not yet domain-aware and won't check constraints associated with domain values. I'd suggest declaring generate_session_id() to return plain text, so that the domain coercion a

[BUGS] BUG #1324: create domain strange behaviour

2004-11-17 Thread PostgreSQL Bugs List
The following bug has been logged online: Bug reference: 1324 Logged by: Tzvetan Tzankov Email address: [EMAIL PROTECTED] PostgreSQL version: 8.0 Beta Operating system: Debian Description:create domain strange behaviour Details: I will post a sort test test=#

[BUGS] Faild to install PostgresQL 8 beta 4 on WinXP with SP2

2004-11-17 Thread Sóvári Péter
Title: Faild to install PostgresQL 8 beta 4 on WinXP with SP2 Hi, I attemted to install PostgresQL 8 beta 4 on WinXP with SP2, but it was failed with 2755 error code. What does it mean? I have searched the archive, but i havn't found anything about this issue. I left every setup option

Re: [BUGS] plperl crashes backend

2004-11-17 Thread Michael Fuhr
I've come up with a simpler test case: CREATE OR REPLACE FUNCTION foo(INTEGER) RETURNS INTEGER AS $$ my @a = 1..$_[0]; elog INFO, "array has $_[0] elements"; return $_[0]; $$ LANGUAGE plperl; Here's the Solaris 9 failure mode: test=> select foo(131); -- works consistently INFO: a