Marcin Kaminski ([EMAIL PROTECTED]) reports a bug with a severity of 3
The lower the number the more severe it is.
Short Description
COMMENT ON DATABASE depends on current database
Long Description
PostgreSQL has mechanism for commenting databases.
Database comments can by read by obj_description
I've upgraded my DB to 7.3.1 from 7.2. The following update causes the SEQ
SCAN instead of INDEX SCAN (in 7.2 there was no bug like that):
create table machines(
i_sprzetx int,
mod char(10),
type char(30)
);
create table sprzetx(
rowid int,
ident char(50)
);
create index i_sprzetx on sprzet
POSTGRESQL BUG REPORT TEMPLATE
Your name : Roman (Averk) Grits
Your email address : [EMAIL PROTECTED]
System Configu
Allan Oepping ([EMAIL PROTECTED]) reports a bug with a severity of 3
The lower the number the more severe it is.
Short Description
floor function returning double precision with integer arguments in 7.3, returns
numeric in 7.2 with the same statement
Long Description
Return datatype of the floor
Dear Sir,
I have downloaded fallowing files from http://www.postgresql.org
1. mx-2.0.1-1.i386.rpm
2. postgresql-odbc-7.1.2-5PGDG.i386.rpm
3. postgresql-7.1.2-5PGDG.i386.rpm
4. postgresql-perl-7.1.2-5PGDG.i386.rpm
5. postgresql-contrib-7.1.2-5PGDG.i386.rpm
6. postgresql-python-7.1.2-5PGDG.i386.rpm
On Mon, 20 Jan 2003 03:13:38 -0500 (EST)
[EMAIL PROTECTED] wrote:
> strings without any unnecessary padding zeroes. I use a usual
> postgresql*-7.3.1-1PGDG.i386.rpm taken from your site, if it makes
> sense. Please take a look into this.
>
> Sample Code
> The following line:
>
> SELECT 1875/1000
[EMAIL PROTECTED] writes:
> Return datatype of the floor function is different between PostgreSQL 7.2 and
>PostgreSQL 7.3 the documentation for PostgreSQL 7.3 states that PostgreSQL 7.3's
>floor function should return type numeric. In 7.3 it seems to be returning the double
>precision datatype.
On Thursday 16 January 2003 07:58, Sharanayya G M wrote:
> [root@majcompnew p7.2]# rpm -i postgresql-contrib-7.1.2-5PGDG.i386.rpm
> error: failed dependencies:
> postgresql = 7.1.2 is needed by postgresql-contrib-7.1.2-5PGDG
> libcrypto.so.1 is needed by postgresql-contrib-7.1.2-5
"Ace" <[EMAIL PROTECTED]> writes:
> I've upgraded my DB to 7.3.1 from 7.2. The following update causes the SEQ
> SCAN instead of INDEX SCAN (in 7.2 there was no bug like that):
I don't believe that. No version of Postgres would have generated an
index scan on this query, because you've got a type
