[BUGS] BUG #1707: statistics collector starts with stats_start_collector = false

2005-06-12 Thread Federico Di Gregorio
The following bug has been logged online: Bug reference: 1707 Logged by: Federico Di Gregorio Email address: [EMAIL PROTECTED] PostgreSQL version: 7.4.8 Operating system: Debian GNU/Linux Description:statistics collector starts with stats_start_collector = false Detai

[BUGS] BUG #1713: dbmirror replaces nextval, setval functions

2005-06-12 Thread James Doherty
The following bug has been logged online: Bug reference: 1713 Logged by: James Doherty Email address: [EMAIL PROTECTED] PostgreSQL version: 8.0.3 Operating system: Solaris 8 Intel Description:dbmirror replaces nextval, setval functions Details: The dbmirror contrib

[BUGS] BUG #1708: Weekly news link error

2005-06-12 Thread DouDou
The following bug has been logged online: Bug reference: 1708 Logged by: DouDou Email address: [EMAIL PROTECTED] PostgreSQL version: 8.0.3 Operating system: RH9 Description:Weekly news link error Details: The URL for lastest weekly new June 6th,2005 is error. no doc

[BUGS] BUG #1716: FATAL: XX000: failed to initialize lc_messages to ""

2005-06-12 Thread steve owen
The following bug has been logged online: Bug reference: 1716 Logged by: steve owen Email address: [EMAIL PROTECTED] PostgreSQL version: 7.4.8 Operating system: RHEL4 Description:FATAL: XX000: failed to initialize lc_messages to "" Details: I found this referenced

[BUGS] BUG #1711: psql doesn't format nicely with newlines

2005-06-12 Thread
The following bug has been logged online: Bug reference: 1711 Logged by: Email address: [EMAIL PROTECTED] PostgreSQL version: 8.0.3 Operating system: Debian Linux Description:psql doesn't format nicely with newlines Details: Printing fields with newline characters

[BUGS] BUG #1712: JDBC column precision for bigint is 0

2005-06-12 Thread Gilles Dubochet
The following bug has been logged online: Bug reference: 1712 Logged by: Gilles Dubochet Email address: [EMAIL PROTECTED] PostgreSQL version: 8.0.2 Operating system: Linux Description:JDBC column precision for bigint is 0 Details: Whith the JDBC driver at least up t

[BUGS] BUG #1705: nextval being evaluated more than once

2005-06-12 Thread Nick Farrell
The following bug has been logged online: Bug reference: 1705 Logged by: Nick Farrell Email address: [EMAIL PROTECTED] PostgreSQL version: 8.0.3 Operating system: ubuntu linux (warty warthog) Description:nextval being evaluated more than once Details: If I use embed

[BUGS] BUG #1710: Not clear instruction abnout jdbc driver.

2005-06-12 Thread Placek
The following bug has been logged online: Bug reference: 1710 Logged by: Placek Email address: [EMAIL PROTECTED] PostgreSQL version: 8.0.3 Operating system: Linux Description:Not clear instruction abnout jdbc driver. Details: The information in file: ftp://ftp7.pl.p

[BUGS] BUG #1714: dbmirror replaces nextval, setval functions

2005-06-12 Thread James Doherty
The following bug has been logged online: Bug reference: 1714 Logged by: James Doherty Email address: [EMAIL PROTECTED] PostgreSQL version: 8.0.3 Operating system: Solaris 8 Intel Description:dbmirror replaces nextval, setval functions Details: The dbmirror contrib

Re: [BUGS] BUG #1678: pw_shadow BUS ERROR

2005-06-12 Thread Haluk GUNCER
Tom, My problem is solved! I compiled postgresql 8.0.3 on HP test drive machine. Then it worked succesfully. I tar'ed and copied the generated code to our server , and it worked. I suggest to put binaries for each vendor to this website for downloading so that we wont waste out time for co

[BUGS] BUG #1704: Download problems

2005-06-12 Thread Igor
The following bug has been logged online: Bug reference: 1704 Logged by: Igor Email address: [EMAIL PROTECTED] PostgreSQL version: NA Operating system: OS is NA Description:Download problems Details: Hello, this problem is not related to postgresql code. It is rela

[BUGS] pg_dump: [tar archiver] could not write to tar member error

2005-06-12 Thread filip filipov
Hello! I'm using PostgreSQL 8.0.2. PG_DUMP can create the backup tar file. "pg_dump: [tar archiver] could not write to tar member (wrote 2279, attempted 7211)" the command I use is: "pg_dump -Ft -Upostgres -b databasename > /var/tmp/backup.tar" I've been using postgresql 7.4.2 before and the bac

[BUGS] BUG #1709: upper(), lower() don't work with UTF-8

2005-06-12 Thread Constantin Dunayev
The following bug has been logged online: Bug reference: 1709 Logged by: Constantin Dunayev Email address: [EMAIL PROTECTED] PostgreSQL version: 7.x, 8.0.x Operating system: Linux, maybe others Description:upper(), lower() don't work with UTF-8 Details: Functions, s

[BUGS] bug

2005-06-12 Thread Juliano Francisco Angeli
Hello, I am writing again to say that I want to install in the Windows 98 with the Cygwin. The version of the Postgresql is 7,4,3. Did not say in the previous email. I am thankful again. Juliano -- * * Juliano Francisco Angeli

[BUGS] bug

2005-06-12 Thread Juliano Francisco Angeli
Hello, I am installing postgresql in the Windows 98 with the Cygwin, I am using the FAQ http://www.postgresql.org/docs/faqs.FAQ_CYGWIN.html for orientation. When I make as the command initdb - D/usr/local/pgsql/data - W - and LATIN1 appears the error: initdb - failed. It would like aid, b

[BUGS] BUG #1703: dns for ftp mirrors messed up

2005-06-12 Thread Tavis Rudd
The following bug has been logged online: Bug reference: 1703 Logged by: Tavis Rudd Email address: [EMAIL PROTECTED] PostgreSQL version: any Operating system: any Description:dns for ftp mirrors messed up Details: none of the ftp mirrors are currently accessible do

Re: [BUGS] pg_dump: [tar archiver] could not write to tar member error

2005-06-12 Thread Tom Lane
"filip filipov" <[EMAIL PROTECTED]> writes: > I'm using PostgreSQL 8.0.2. PG_DUMP can create the backup tar file. > "pg_dump: [tar archiver] could not write to tar member (wrote 2279, > attempted 7211)" > the command I use is: "pg_dump -Ft -Upostgres -b databasename > > /var/tmp/backup.tar" Are y

Re: [BUGS] BUG #1707: statistics collector starts with stats_start_collector = false

2005-06-12 Thread Tom Lane
"Federico Di Gregorio" <[EMAIL PROTECTED]> writes: > If the following combinatio of parameters is used: > stats_start_collector = false > stats_row_level = true > the collector process is started even if the documentation says that "The > parameter stats_start_collector must be set to true for th

Re: [BUGS] BUG #1712: JDBC column precision for bigint is 0

2005-06-12 Thread Oliver Jowett
Gilles Dubochet wrote: > The following bug has been logged online: > > Bug reference: 1712 > Logged by: Gilles Dubochet > Email address: [EMAIL PROTECTED] > PostgreSQL version: 8.0.2 > Operating system: Linux > Description:JDBC column precision for bigint is 0 > Detail

[BUGS] could not connect to server: [then mess]

2005-06-12 Thread Dan Jacobson
It's my first time using postgresql, and I might as well tell you my first impressions. I am reading /usr/share/doc/postgresql/html/tutorial-createdb.html and try $ createdb mydb 2>&1|cat -v createdb: could not connect to database template1: could not connect to server: [EMAIL PROTECTED]&@^S

Re: [BUGS] BUG #1707: statistics collector starts with stats_start_collector

2005-06-12 Thread Bruce Momjian
Tom Lane wrote: > "Federico Di Gregorio" <[EMAIL PROTECTED]> writes: > > If the following combinatio of parameters is used: > > > stats_start_collector = false > > stats_row_level = true > > > the collector process is started even if the documentation says that "The > > parameter stats_start_coll

Re: [BUGS] BUG #1707: statistics collector starts with stats_start_collector = false

2005-06-12 Thread Tom Lane
Bruce Momjian writes: > If that is the logic, why do we have stats_start_collector at all? Ask Jan ;-) I can see some advantage to it as a way of finding out whether the collector was started or not ... but if that's the intent, we should make it non user-writable. rega

Re: [BUGS] BUG #1707: statistics collector starts with stats_start_collector

2005-06-12 Thread Bruce Momjian
Tom Lane wrote: > Bruce Momjian writes: > > If that is the logic, why do we have stats_start_collector at all? > > Ask Jan ;-) > > I can see some advantage to it as a way of finding out whether the > collector was started or not ... but if that's the intent, we > should make it non user-writabl

Re: [BUGS] BUG #1707: statistics collector starts with stats_start_collector = false

2005-06-12 Thread Tom Lane
Bruce Momjian writes: > I can see someone turning it off but leaving other options on because > they will want to turn them on later. "later" when? It's not useful to try to turn on stats_start_collector after postmaster start, because the UDP socket won't exist. regards

Re: [BUGS] BUG #1707: statistics collector starts with stats_start_collector

2005-06-12 Thread Bruce Momjian
Tom Lane wrote: > Bruce Momjian writes: > > I can see someone turning it off but leaving other options on because > > they will want to turn them on later. > > "later" when? It's not useful to try to turn on stats_start_collector > after postmaster start, because the UDP socket won't exist. Lat

Re: [BUGS] BUG #1707: statistics collector starts with stats_start_collector = false

2005-06-12 Thread Tom Lane
Bruce Momjian writes: > Later such as in a later postmaster start, but personally I would just > remove the option completely. I don't have a problem with removing it as a writable option ... but I'm thinking we should leave it as a read-only GUC parameter (like the several others we have already

Re: [BUGS] BUG #1707: statistics collector starts with stats_start_collector

2005-06-12 Thread Bruce Momjian
Tom Lane wrote: > Bruce Momjian writes: > > Later such as in a later postmaster start, but personally I would just > > remove the option completely. > > I don't have a problem with removing it as a writable option ... but > I'm thinking we should leave it as a read-only GUC parameter (like > the

Re: [BUGS] BUG #1707: statistics collector starts with stats_start_collector = false

2005-06-12 Thread Tom Lane
Bruce Momjian writes: > Tom Lane wrote: >> I don't have a problem with removing it as a writable option ... but >> I'm thinking we should leave it as a read-only GUC parameter (like >> the several others we have already). Otherwise we'll need to add some >> other method of finding out whether the