Re: [BUGS] recent (just got from cvs) build doesn't run nicely

Hubert depesz Lubaczewski <[EMAIL PROTECTED]> writes: > i just got newest checkout from cvs. > it builded fine. > [but] > initializing pg_depend... /home/pgdba/work/bin/initdb: line 716: 26438 Segmentation >fault "$PGPATH"/postgres $PGSQL_OPT template1 >/dev/null

Re: [BUGS] Bug #880: COMMENT ON DATABASE depends on current

> > I tend to think that the functionality to give comments to databases > > should either be redone to work right (for example by storing the comment > > in a global table (but think about the encoding problems)) or be ripped > > out. Right now the feature to give a comment to a database you pres

Re: [BUGS] Bug #880: COMMENT ON DATABASE depends on current database

Peter Eisentraut wrote: > Bruce Momjian writes: > > > Do we have psql -l to connect to all the databases to collect comments? > > I guess we could _try_ to connect to as many databases as possible, but > > it seems a little overly complex to me. What do others think? > > I tend to think that the

Re: [BUGS] Bug #880: COMMENT ON DATABASE depends on current database

Bruce Momjian writes: > Do we have psql -l to connect to all the databases to collect comments? > I guess we could _try_ to connect to as many databases as possible, but > it seems a little overly complex to me. What do others think? I tend to think that the functionality to give comments to dat

[BUGS] recent (just got from cvs) build doesn't run nicely

hi i just got newest checkout from cvs. it builded fine. it installed. than i do initdb: (pgdba@depeszws[pts/11]) 21:35:05 [~] $ echo $PGDATA /home/pgdba/work/data (pgdba@depeszws[pts/11]) 21:35:10 [~] $ initdb -W The files belonging to this database system will be owned by user "pgdba". This use

Re: [BUGS] No migration path for MONEY

Bruce, > They are probably better off just changing the column data type, _and_ > we need someone to get MONEY working as an extented NUMERIC type. Apparently D'Arcy McCain is going to do this. Go, D'arcy! -- -Josh Berkus Aglio Database Solutions San Francisco ---(

Re: [BUGS] No migration path for MONEY

They are probably better off just changing the column data type, _and_ we need someone to get MONEY working as an extented NUMERIC type. --- Josh Berkus wrote: > Folks, > > Bug reported off IRC: > > MONEY Type cannot be ca

Re: [BUGS] No error reported when field in subselect is not part of

On Mon, 27 Jan 2003, Jean-Luc Lachance wrote: > There is no error reported when a field in the subselect is not part of > the subselect table > but exists in the main table. > > Try This: > > nsd=# create table a ( f1 int, f2 text); > CREATE > nsd=# create table b ( f3 int, f4 text); > CREATE > ns

[BUGS] No error reported when field in subselect is not part of the table but exists in the main table.

There is no error reported when a field in the subselect is not part of the subselect table but exists in the main table. Try This: nsd=# create table a ( f1 int, f2 text); CREATE nsd=# create table b ( f3 int, f4 text); CREATE nsd=# select * from a where f1 in ( select f1 from b); f1 | f2 ---

Re: [BUGS] Cursor case-sensitivity

"Key88 SF" <[EMAIL PROTECTED]> writes: > BEGIN; > SELECT reffunc('funcCursor'); > FETCH ALL IN funcCursor; > COMMIT; > WARNING: PerformPortalFetch: portal "funccursor" not found. I don't think this is a bug. You should have written FETCH ALL IN "funcCursor"; regards, to

[BUGS] Cursor case-sensitivity

Not sure if this is known or not, but apparently cursors names are not appropriately case-lowered when dealing with functions that return cursors. Using the example straight from the documentation at http://developer.postgresql.org/docs/postgres/plpgsql-cursors.html: This works: BEGIN; SELECT