[BUGS] libber library not found on RC1

2011-08-25 Thread alexondi
Hi! I update server to RC1 version and after call pg_ctl to start I get this error opt/PostgreSQL/9.1/bin/pg_ctl: error while loading shared libraries: liblber-2.3.so.0: cannot open shared object file: No such file or directory But I have 2.4 version of this library. And I see in ldd pg_ctl that

[BUGS] BUG #6176: pg_dump dumps pg_catalog tables

2011-08-25 Thread Chander Ganesan
The following bug has been logged online: Bug reference: 6176 Logged by: Chander Ganesan Email address: chan...@otg-nc.com PostgreSQL version: 9.0.4 Operating system: Centos 5.6 Description:pg_dump dumps pg_catalog tables Details: Normally, the pg_dump command ignor

Re: [BUGS] libber library not found on RC1

2011-08-25 Thread Tom Lane
alexondi writes: > I update server to RC1 version and after call pg_ctl to start I get this > error > opt/PostgreSQL/9.1/bin/pg_ctl: error while loading shared libraries: > liblber-2.3.so.0: cannot open shared object file: No such file or directory > But I have 2.4 version of this library. And I

Re: [BUGS] libber library not found on RC1

2011-08-25 Thread Dave Page
On Thu, Aug 25, 2011 at 3:17 PM, Tom Lane wrote: > alexondi writes: >> I update server to RC1 version and after call pg_ctl to start I get this >> error > >> opt/PostgreSQL/9.1/bin/pg_ctl: error while loading shared libraries: >> liblber-2.3.so.0: cannot open shared object file: No such file or d

Re: [BUGS] BUG #6176: pg_dump dumps pg_catalog tables

2011-08-25 Thread Tom Lane
"Chander Ganesan" writes: > Normally, the pg_dump command ignored the pg_catalog tables when performing > a dump. However, when provided the '--table' argument it fails to ignore > the pg_catalog table. > For example, suppose I had tables p1-p10 that I wanted to dump, I could use > the following

Re: [BUGS] BUG #6176: pg_dump dumps pg_catalog tables

2011-08-25 Thread Chander Ganesan
On 8/25/11 10:52 AM, Tom Lane wrote: "Chander Ganesan" writes: Normally, the pg_dump command ignored the pg_catalog tables when performing a dump. However, when provided the '--table' argument it fails to ignore the pg_catalog table. For example, suppose I had tables p1-p10 that I wanted to du

Re: [BUGS] BUG #6170: hot standby wedging on full-WAL disk

2011-08-25 Thread Robert Haas
On Mon, Aug 22, 2011 at 2:57 AM, Heikki Linnakangas wrote: > So the problem is that walreceiver merrily writes so much future WAL that it > runs out of disk space? A limit on the maximum number of future WAL files to > stream ahead would fix that, but I can't get very excited about it. Usually > y

[BUGS] BUG #6177: Size field type TEXT

2011-08-25 Thread Claudio Oliveira
The following bug has been logged online: Bug reference: 6177 Logged by: Claudio Oliveira Email address: claudio...@hotmail.com PostgreSQL version: 9.1rc1 Operating system: Windows 7 Description:Size field type TEXT Details: Hello, Use version 8.4 and have no issue

Re: [BUGS] BUG #6177: Size field type TEXT

2011-08-25 Thread Kevin Grittner
"Claudio Oliveira" wrote: > Use version 8.4 and have no issues with the field type TEXT. > > In version 9.1rc1 is limited to 4680 characters. > > Where do I change that size? test=# create table txt (val text); CREATE TABLE test=# insert into txt values (repeat('long string', 100)); INSE

Re: [BUGS] BUG #6170: hot standby wedging on full-WAL disk

2011-08-25 Thread Heikki Linnakangas
On 25.08.2011 19:11, Robert Haas wrote: On Mon, Aug 22, 2011 at 2:57 AM, Heikki Linnakangas wrote: So the problem is that walreceiver merrily writes so much future WAL that it runs out of disk space? A limit on the maximum number of future WAL files to stream ahead would fix that, but I can't

Re: [BUGS] BUG #6177: Size field type TEXT

2011-08-25 Thread Bruce Momjian
Kevin Grittner wrote: > "Claudio Oliveira" wrote: > > > Use version 8.4 and have no issues with the field type TEXT. > > > > In version 9.1rc1 is limited to 4680 characters. > > > > Where do I change that size? > > test=# create table txt (val text); > CREATE TABLE > test=# insert into txt v

Re: [BUGS] BUG #6169: a non fatal error occured during cluster.... problem with environment variables

2011-08-25 Thread Dave Page
On Fri, Aug 19, 2011 at 2:19 PM, ondro wrote: > > The following bug has been logged online: > > Bug reference:      6169 > Logged by:          ondro > Email address:      balu...@horizon.sk > PostgreSQL version: 8.4.8 > Operating system:   WindowsXP > Description:        a non fatal error occured

Re: [BUGS] BUG #6170: hot standby wedging on full-WAL disk

2011-08-25 Thread Daniel Farina
On Thu, Aug 25, 2011 at 10:16 AM, Heikki Linnakangas wrote: > On 25.08.2011 19:11, Robert Haas wrote: >> >> On Mon, Aug 22, 2011 at 2:57 AM, Heikki Linnakangas >>  wrote: >>> >>> So the problem is that walreceiver merrily writes so much future WAL that >>> it >>> runs out of disk space? A limit o

Re: [BUGS] BUG #6177: Size field type TEXT

2011-08-25 Thread Claudio Oliveira
Hello, I'm doing the test in PGAdmin. Must be a bug in PGAdmim. I'm sorry I have not tested in psql create table txt (val text); txt insert into values ​​(repeat ('x', 4500)); char_length select (val) from txt; txt insert into values ​​(repeat ('x', 4685)); char_length select (val) from txt;

Re: [BUGS] BUG #6177: Size field type TEXT

2011-08-25 Thread Kevin Grittner
Claudio Oliveira wrote: > I'm doing the test in PGAdmin. > > Must be a bug in PGAdmim. > > I'm sorry I have not tested in psql > > create table txt (val text); > txt insert into values ​​(repeat ('x', 4500)); > char_length select (val) from txt; > txt insert into values ​​(repeat ('x', 4685))

[BUGS] BUG #6178: date_trunc : interval units "week" not supported contradicts documentation

2011-08-25 Thread Noah Hamerslough
The following bug has been logged online: Bug reference: 6178 Logged by: Noah Hamerslough Email address: n...@pcc.com PostgreSQL version: 8.4 Operating system: Windows Vista Description:date_trunc : interval units "week" not supported contradicts documentation Details