[BUGS] Bug in pgAdminIII or in pg 8 beta3 ?

2004-11-04 Thread Luiz K. Matsumura
Hi I think that is can be a bug... When I create a new database in pg8 beta3 (win32) like this CREATE DATABASE test WITH OWNER = admin ENCODING = 'UNICODE'; System objects became visible in public schema : tables like pg_ts_cfg , pg_ts_cfgmap, pg_ts_dict ... functions , operators etc. but

Re: [BUGS] Bug in pgAdminIII or in pg 8 beta3 ?

2004-11-04 Thread Oliver Elphick
On Thu, 2004-11-04 at 13:06, Luiz K. Matsumura wrote: > Hi > > I think that is can be a bug... When I create a new database in pg8 > beta3 (win32) like this > > CREATE DATABASE test > WITH OWNER = admin >ENCODING = 'UNICODE'; > > System objects became visible in public schema : > tabl

Re: [BUGS] could not find /usr/local/timezone

2004-11-04 Thread Tom Lane
Josh Berkus <[EMAIL PROTECTED]> writes: >> As best I can tell, this is coming out because pgtz.c thinks that >> /usr/share/timezone is where Postgres' own timezone files are; which >> implies that get_share_directory() is returning /usr/share; which does >> not make a lot of sense. > Nope: > $ .

[BUGS] Concatenating strings within a function definition

2004-11-04 Thread Nishad Prakash
I'm trying to create a function like so: create function get_lid_prefix (text) returns setof int as 'select lid from ilemma where lemma ~ \'^\' + upper($1)' language 'sql'; I've tried several variations, including 'select lid from ilemma where lemma ~ ' || '^' || ' upper ($1)' 'select lid from

Re: [BUGS] Concatenating strings within a function definition

2004-11-04 Thread Tom Lane
Nishad Prakash <[EMAIL PROTECTED]> writes: > I'm trying to create a function like so: > create function get_lid_prefix (text) returns setof int as > 'select lid from ilemma where lemma ~ \'^\' + upper($1)' > language 'sql'; 'select lid from ilemma where lemma ~ (\'^\' || upper($1))'

[BUGS] a bug in plpgsql

2004-11-04 Thread Jaime Casanova
Hi guys, i'm testing a v8.0beta4 in windows. Welcome to psql 8.0.0beta4, the PostgreSQL interactive terminal. Type: \copyright for distribution terms \h for help with SQL commands \? for help with psql commands \g or terminate with semicolon to execute query \q to qu

Re: [BUGS] a bug in plpgsql

2004-11-04 Thread Tom Lane
Jaime Casanova <[EMAIL PROTECTED]> writes: > CASE rs_dtran.fpg_codigo > WHEN ''EF'' THEN > IF rs_ttran.tra_tipo = ''+'' THEN > valo

Re: [BUGS] a bug in plpgsql

2004-11-04 Thread Jaime Casanova
--- Tom Lane <[EMAIL PROTECTED]> escribió: > Jaime Casanova <[EMAIL PROTECTED]> writes: > > CASE rs_dtran.fpg_codigo > > WHEN ''EF'' THEN > > IF rs_ttran.tra_tipo = ''+'' THEN > >

Re: [BUGS] a bug in plpgsql

2004-11-04 Thread Tom Lane
Jaime Casanova <[EMAIL PROTECTED]> writes: > --- Tom Lane <[EMAIL PROTECTED]> escribió: >> if/then/else is a statement, not a component of an >> expression. >> CASE is an expression construct, not a statement. I >> think >> you need to rewrite the CASE as an if/then/elsif >> statement. > I will

Re: [BUGS] a bug in plpgsql

2004-11-04 Thread Jaime Casanova
--- Tom Lane <[EMAIL PROTECTED]> escribió: > Jaime Casanova <[EMAIL PROTECTED]> writes: > > --- Tom Lane <[EMAIL PROTECTED]> escribió: > >> if/then/else is a statement, not a component of > an > >> expression. > >> CASE is an expression construct, not a statement. > I > >> think > >> you need

Re: [BUGS] a bug in plpgsql

2004-11-04 Thread Tom Lane
Jaime Casanova <[EMAIL PROTECTED]> writes: > --- Tom Lane <[EMAIL PROTECTED]> escribió: >> It most certainly did not work in 7.4.2, or any >> other PG release. >> plpgsql doesn't have a CASE statement. > This is a production server... and the same script... > (It was an error in v7.4.2 to permit

Re: [BUGS] a bug in plpgsql

2004-11-04 Thread Jaime Casanova
--- Tom Lane <[EMAIL PROTECTED]> escribió: > Jaime Casanova <[EMAIL PROTECTED]> writes: > > --- Tom Lane <[EMAIL PROTECTED]> escribió: > >> It most certainly did not work in 7.4.2, or any > >> other PG release. > >> plpgsql doesn't have a CASE statement. > > > This is a production server... an

Re: [BUGS] Bug in pgAdminIII or in pg 8 beta3 ?

2004-11-04 Thread Simon Riggs
On Thu, 2004-11-04 at 13:49, Oliver Elphick wrote: > On Thu, 2004-11-04 at 13:06, Luiz K. Matsumura wrote: > > Hi > > > > I think that is can be a bug... When I create a new database in pg8 > > beta3 (win32) like this > > > > CREATE DATABASE test > > WITH OWNER = admin > >ENCODING = 'U

Re: [BUGS] Bug in pgAdminIII or in pg 8 beta3 ?

2004-11-04 Thread Magnus Hagander
>> No bug; these objects exist in the template1 database - >someone created >> them there - so they get copied into every new database. This is a >> _feature_. It lets you ensure that every new database >contains certain >> objects. >> > >I believe tsearch2 is part of the install in Magnus' .m

Re: [BUGS] could not find /usr/local/timezone

2004-11-04 Thread Tom Lane
"Josh Berkus" <[EMAIL PROTECTED]> writes: >> What it looks like is that the postmaster was executed out of >> /usr/bin. > dropping symlinks to the pg binaries in /usr/bin or > /usr/local/bin or /sbin/ is something I've done for ages, on PostgreSQL > versions 7.1 -> 7.4. Is there a problem with t

Re: [BUGS] could not find /usr/local/timezone

2004-11-04 Thread Josh Berkus
Tom, > What it looks like is that the postmaster was executed out of /usr/bin. > Have you got any symlinks you aren't telling us about? ÂWhere does that > mount point to, anyway? Yes, there are symlinks in /usr/bin to /usr/local/pgsql/bin. I've never had it cause issues before, though. H

Re: [BUGS] could not find /usr/local/timezone

2004-11-04 Thread Josh Berkus
Tom, > This is fundamentally broken by the changes to support relocatable > installs: PG now attempts to find the support files by relative paths > from the place where the executable was found. OK, I can see the tradeoff.Hmmm ... this means that we need something in the Release Notes, I wou

Re: [BUGS] could not find /usr/local/timezone

2004-11-04 Thread Peter Eisentraut
Tom Lane wrote: > This is fundamentally broken by the changes to support relocatable > installs: PG now attempts to find the support files by relative paths > from the place where the executable was found. I recall that on some systems the "normal" method of installation is installing everything

Re: [BUGS] could not find /usr/local/timezone

2004-11-04 Thread Bruce Momjian
Is this an open 8.0 item? --- Peter Eisentraut wrote: > Tom Lane wrote: > > This is fundamentally broken by the changes to support relocatable > > installs: PG now attempts to find the support files by relative paths > > fr

Re: [BUGS] could not find /usr/local/timezone

2004-11-04 Thread Tom Lane
Peter Eisentraut <[EMAIL PROTECTED]> writes: > Tom Lane wrote: >> This is fundamentally broken by the changes to support relocatable >> installs: PG now attempts to find the support files by relative paths >> from the place where the executable was found. > I recall that on some systems the "norma