Re: [BUGS] BUG #5184: default tablespace owner is not dumped

2009-11-12 Thread Tom Lane
"Robert Haas" writes: > The following command does not change the output of "pg_dumpall": > alter tablespace pg_default owner to bob; I don't think this is a bug. It's one specific aspect of a general principle that system objects don't get dumped. If they did, using pg_dump to upgrade across m

[BUGS] BUG #5184: default tablespace owner is not dumped

2009-11-12 Thread Robert Haas
The following bug has been logged online: Bug reference: 5184 Logged by: Robert Haas Email address: robertmh...@gmail.com PostgreSQL version: CVS HEAD Operating system: Linux Description:default tablespace owner is not dumped Details: The following command does not

Re: [BUGS] BUG #5183: Wrong select results using multicolumn gin indexes

2009-11-12 Thread Tom Lane
"Yury Don" writes: > mdb=# create table tmp (id integer not null primary key, t tsvector, i > integer); > CREATE TABLE > mdb=# insert into tmp values (1, 'word', 66); > INSERT 0 1 > mdb=# create index tmp_idx on tmp using gin (t, i); > CREATE INDEX > mdb=# insert into tmp values (2, 'word', 86); >

Re: [BUGS] BUG #5182: query with deferents results

2009-11-12 Thread Tom Lane
"artur saldanha" writes: > PostgreSQL 8.3.5 on x86_64-redhat-linux-gnu, compiled by GCC gcc (GCC) 4.3.2 > 20081007 (Red Hat 4.3.2-6 > this query presents 7 rows... > SELECT * >FROM ( (SELECT n.nrnota, i.cdproduto, i.qtde as batata, i.vrpunit, > n.cdfinalidade, cdnrnota >FROM nfisca

Re: [BUGS] BUG #5182: query with deferents results

2009-11-12 Thread Stephan Szabo
On Thu, 12 Nov 2009, artur saldanha wrote: > > The following bug has been logged online: > > Bug reference: 5182 > Logged by: artur saldanha > Email address: artur.salda...@gmail.com > PostgreSQL version: 8.3.5 > Operating system: Fedora 64 > Description:query with de

[BUGS] BUG #5181: query with deferents results

2009-11-12 Thread Artur Saldanha
The following bug has been logged online: Bug reference: 5181 Logged by: Artur Saldanha Email address: artur.salda...@gmail.com PostgreSQL version: 8.3.5 Operating system: Fedora 64 Description:query with deferents results Details: PostgreSQL 8.3.5 on x86_64-redhat-

[BUGS] BUG #5182: query with deferents results

2009-11-12 Thread artur saldanha
The following bug has been logged online: Bug reference: 5182 Logged by: artur saldanha Email address: artur.salda...@gmail.com PostgreSQL version: 8.3.5 Operating system: Fedora 64 Description:query with deferents results Details: PostgreSQL 8.3.5 on x86_64-redhat

[BUGS] BUG #5183: Wrong select results using multicolumn gin indexes

2009-11-12 Thread Yury Don
The following bug has been logged online: Bug reference: 5183 Logged by: Yury Don Email address: y...@vpcit.ru PostgreSQL version: 8.4.1 Operating system: Debian Linux (architecture amd64) Description:Wrong select results using multicolumn gin indexes Details: We ar

Re: [BUGS] BUG #5180: How to get only User created tables by using SQLTables() in ODBC

2009-11-12 Thread Pavel Stehule
2009/11/12 Jitendra Lenka : > > The following bug has been logged online: > > Bug reference:      5180 > Logged by:          Jitendra Lenka > Email address:      jitendra.le...@csqldb.com > PostgreSQL version: 8.3.3 > Operating system:   Fedora10 > Description:        How to get only User created t

Re: [BUGS] BUG #5171: Composite type with array does not translate in plpythonu

2009-11-12 Thread Peter Eisentraut
On lör, 2009-11-07 at 12:23 +0200, Peter Eisentraut wrote: > On fre, 2009-11-06 at 17:29 +, Jason wrote: > > When I have a plpythonu function returning a composite type that has an > > array column, the function does not work when I try to return a list for > > that column. > > There is a patc

[BUGS] BUG #5180: How to get only User created tables by using SQLTables() in ODBC

2009-11-12 Thread Jitendra Lenka
The following bug has been logged online: Bug reference: 5180 Logged by: Jitendra Lenka Email address: jitendra.le...@csqldb.com PostgreSQL version: 8.3.3 Operating system: Fedora10 Description:How to get only User created tables by using SQLTables() in ODBC Details: