The following bug has been logged online:
Bug reference: 1577
Logged by: Roman Schayuk
Email address: [EMAIL PROTECTED]
PostgreSQL version: 7.2.2
Operating system: RedHat Linux 8.0 x86
Description:round(dp) function does not round to nearest integer
properly
Details:
Hello pgsql-bugs,
Excuse my English. I'm from Russia.
I understood, that following is implementation behavior,
but this is really not what i'm expecting to see.
--Start test--
create table try1
(
id serial PRIMARY KEY,-- same with DEFAULT nextval('some_sequence')
info varchar(
The following bug has been logged online:
Bug reference: 1581
Logged by: Marcus v. Scotti
Email address: [EMAIL PROTECTED]
PostgreSQL version: 7.4.7
Operating system: Linux
Description:Problem with capitalised DB names...
Details:
When trying to grant database privi
Hello pgsql-bugs,
Excuse my English. I'm from Russia.
I realized i forgotten to write version of PostgreSQL in previous letter.
I'm using PostgreSQL 8.0.1 on Windows and Slackware 10.0 compilled with gcc
3.3.4
I understood, that following is implementation behavior,
but this is really not what i
The following bug has been logged online:
Bug reference: 1578
Logged by: Celia McInnis
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0.1
Operating system: Linux
Description:::bit(n) behaves "differently" if applied to bit strings
than integers.
Details:
It'
The following bug has been logged online:
Bug reference: 1582
Logged by: Eric McGough
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0.1
Operating system: Solaris 8
Description:boolean DEFAULT TRUE results in FALSE for NULL values
Details:
-- This table and
The following bug has been logged online:
Bug reference: 1580
Logged by: David Elliott
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0.1
Operating system: Mac OS X 10.3.8
Description:pg_dumpall aborts when cwd is unreadable
Details:
After setting up a cron
Dear
Postgre team,
My
name is Mladen Mitev.
I
downloaded and installed Postgre SQL 8.0.1 and I found that it did not work with
Win1251 (Cyrillic). It did not translate the capital and small
letters.
These
commands did not work:
ILIKE
lower()
upper()
By
example:
1.
create table t1 (c
The following bug has been logged online:
Bug reference: 1592
Logged by: Gabor Berenyi
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0.0
Operating system: i86 Debian Linux 2.4.20
Description:"with hold" cursor problem
Details:
begin;
declare t cursor with
Hello pgsql-bugs,
I'm here again. I'm using PostgreSQL 8.0.1 on Windows and Linux Slackware 10.0
--Start test--
create sequence try3_seq;
create table try3
(
id int PRIMARY KEY,
info varchar(30)
)
without oids;
create table try4
(
id int,
info varchar(30)
)
wit
The following bug has been logged online:
Bug reference: 1588
Logged by: Lionel Bouton
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0.1
Operating system: Linux 2.6, glibc 2.3.4
Description:pg_autovacuum sleep parameter overflow
Details:
pg_autovacuum doesn
The following bug has been logged online:
Bug reference: 1591
Logged by: Michael Williamson
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0.1
Operating system: Windows 2000
Description:BETWEEN NULL AND NULL causes crash
Details:
Hello,
I have the following
The following bug has been logged online:
Bug reference: 1579
Logged by: Byron Zambrano
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0.1
Operating system: Win Xp Service Pack 2
Description:DO NOT CONNECT
Details:
Hello my name is Byron Zambrano I like prog
The following bug has been logged online:
Bug reference: 1590
Logged by: Michaela
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0.1
Operating system: SuSE Linux 9.1
Description:Comparison Operation with Strings
Details:
Hello!
conditions:
---
Our d
I found an odd behaviour, which I believe it is a bug, and for us it is
a serious matter. Can anyone on a platform or version other than
PostgreSQL 8.0.1 on Windows XP Advanced Server check if you can
reproduce the finding on your server?
Tables with columns specified as numeric using a domain
The following bug has been logged online:
Bug reference: 1587
Logged by: Ezequiel Tolnay
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0.1
Operating system: Windows XP Advanced Server
Description:Unexpected behaviour of numeric datatype when mixed with
float4
The following bug has been logged online:
Bug reference: 1586
Logged by: Preethi
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0.1
Operating system: Win 2K Pro
Description:Rollback of installation during a silent install with
-qn option
Details:
Hi,
We are
I have already told you the exact command I am using - twice. I identified
the problem in my previous email, and how to reproduce it. If you don't have
a system with Windows 2000 then find someone who does. They will then
confirm what I say.
I resent the implication in your emails that I am some
The following bug has been logged online:
Bug reference: 1584
Logged by: Benjamin Reed
Email address: [EMAIL PROTECTED]
PostgreSQL version: 7.3.9
Operating system: Mac OS X 10.4.0 ("Tiger")
Description:undefined symbol _tas
Details:
Something has changed between 10.
>The following bug has been logged online:
>
>Bug reference: 1586
>Logged by: Preethi
>Email address: [EMAIL PROTECTED]
>PostgreSQL version: 8.0.1
>Operating system: Win 2K Pro
>Description:Rollback of installation during a silent
>install with
>-qn option
>Details:
>
>The following bug has been logged online:
>
>Bug reference: 1579
>Logged by: Byron Zambrano
>Email address: [EMAIL PROTECTED]
>PostgreSQL version: 8.0.1
>Operating system: Win Xp Service Pack 2
>Description:DO NOT CONNECT
>Details:
>
>Hello my name is Byron Zambrano I
"Roman Schayuk" <[EMAIL PROTECTED]> writes:
> gap=> select round(42.5);
> round
> ---
> 42
> (1 row)
> Result has to be 43
No, the above is perfectly correct and in fact required by the IEEE
standard for floating-point arithmetic (because round-to-nearest-even
is the default rounding mode
"Eric McGough" <[EMAIL PROTECTED]> writes:
> -- This table and COPY command should result in all
> -- three columns defaulting to TRUE based on NULL
> -- inputs, but they all result in FALSE. Not sure why?
No, it's filling with NULL, which is what the input specifies.
rega
"Gabor Berenyi" <[EMAIL PROTECTED]> writes:
> begin;
> declare t cursor with hold for select function() as x from R;
> commit;
> Documentation says that the rows represented by a held cursor are copied
> into a temporary file or memory area, but they are not, if they are results
> of a function
"Michaela" <[EMAIL PROTECTED]> writes:
> Our database is defined with SQL_ASCII. We also tested Latin1.
This is determined by locale, not encoding. I suspect you have a
non-C locale selected.
regards, tom lane
---(end of broadcast)
On Thu, 7 Apr 2005, Michaela wrote:
> The following bug has been logged online:
>
> Bug reference: 1590
> Logged by: Michaela
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 8.0.1
> Operating system: SuSE Linux 9.1
> Description:Comparison Operation with Stri
"Michael Williamson" <[EMAIL PROTECTED]> writes:
> SELECT * FROM Entities
> WHERE NULL IS NULL OR (EntityNo BETWEEN NULL AND COALESCE(NULL,NULL))
> This causes one of two results: postmaster crashes or goes into an infinite
> loop.
Good catch. COALESCE(NULL,NULL) is actually broken as far back as
Ezequiel Tolnay <[EMAIL PROTECTED]> writes:
> CREATE DOMAIN currency AS numeric(15,4);
> CREATE TABLE test (id serial, amt currency);
> CREATE FUNCTION f_test(currency) RETURNS currency AS $$
> DECLARE n currency;
> BEGIN n := $1 * 0.2::float4;
>INSERT INTO test (amt) VALUES (n); RETURN n;
"Benjamin Reed" <[EMAIL PROTECTED]> writes:
> Something has changed between 10.3 and 10.4; my PostgreSQL 7.3.9 Fink
> package builds just fine on 10.3, but fails on 10.4 with:
> /usr/bin/ld: Undefined symbols:
> _tas
Perhaps Apple stopped defining __APPLE__ ? Or switched from
__ppc__ to __powerpc
On Wed, Apr 06, 2005 at 11:55:05PM +, John Smith wrote:
>
> I have already told you the exact command I am using - twice.
Could you post links to the messages in the archives where you twice
identified the command? The only complete CREATE TYPE command I
see is in your original message, which
On Tue, Apr 05, 2005 at 18:09:25 +0100,
"Marcus v. Scotti" <[EMAIL PROTECTED]> wrote:
>
> Description:Problem with capitalised DB names...
> Details:
>
> When trying to grant database privileges to a group of users there is no way
> to do this if the database name is capitalised (i.e.
Dobrena Miteva wrote:
> Dear Postgre team,
>
>
>
> My name is Mladen Mitev.
>
> I downloaded and installed Postgre SQL 8.0.1 and I found that it did not work
> with Win1251 (Cyrillic). It did not translate the capital and small letters.
>
> These commands did not work:
>
> ILIKE
>
> lowe
On Mon, 11 Apr 2005 05:57 am, Tom Lane wrote:
> "Roman Schayuk" <[EMAIL PROTECTED]> writes:
> > gap=> select round(42.5);
> > round
> > ---
> > 42
> > (1 row)
> > Result has to be 43
>
> No, the above is perfectly correct and in fact required by the IEEE
> standard for floating-point arit
Tom Lane wrote:
Ezequiel Tolnay <[EMAIL PROTECTED]> writes:
CREATE DOMAIN currency AS numeric(15,4);
CREATE TABLE test (id serial, amt currency);
CREATE FUNCTION f_test(currency) RETURNS currency AS $$
DECLARE n currency;
BEGIN n := $1 * 0.2::float4;
INSERT INTO test (amt) VALUES (n); RETU
David Elliott wrote:
>
> The following bug has been logged online:
>
> Bug reference: 1580
> Logged by: David Elliott
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 8.0.1
> Operating system: Mac OS X 10.3.8
> Description:pg_dumpall aborts when cwd is unreada
On Tue, Apr 05, 2005 at 21:11:12 +0100,
Eric McGough <[EMAIL PROTECTED]> wrote:
>
> COPY my_table FROM STDIN WITH DELIMITER AS '|';
> \N|\N|\N
> \.
COPY doesn't provide a way to use default values for just some rows.
You can get the default for a column by leaving it out of an explicit
column l
Tom Lane wrote:
Perhaps Apple stopped defining __APPLE__ ? Or switched from
__ppc__ to __powerpc__ ? But in any case, updating to PG 7.4
or later should make the problem go away. If you really don't
want to move off 7.3, look in src/backend/storage/lmgr/s_lock.c.
Yeah, I got that far, but was ha
Benjamin Reed <[EMAIL PROTECTED]> writes:
> The strange thing is, it *seems* like both __ppc__ and __powerpc__ are
> defined, and __APPLE__ is definitely defined.
Hmm, then maybe Apple changed something about the assembler syntax,
such that 7.3's "asm" code is failing to define a global symbol?
Russell Smith <[EMAIL PROTECTED]> writes:
> Either way 8.0.1 round differently;
The rounding is the same. The difference from 7.2 is that the unadorned
literal "42.5" is now considered to be numeric whereas 7.2 treated it as
float8. This changed quite some time ago (in 7.3 it looks like).
Bruce Momjian writes:
> The code right now tests for 'cwd' first and just errors out if it can't
> find it. Is it worth refactoring it so you can run pg_dumpall from a
> directory you can't view? Instead of checking 'cwd' right at the start
> we would have to find it only when we need it, and in
Can anybody else with a Windows system reproduce the
problem? The messages in the links above are said to contain enough
information to do so.
windows XP pro SP2
PostgreSQL 8.0.1
this is working for me (but not tested on win 2000 system):
CREATE TYPE product AS (name varchar, price numeric);
41 matches
Mail list logo
