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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
"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
"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
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
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
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
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
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
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
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
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
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
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
28 matches
Mail list logo