Your name : Andriy I Pilipenko
Your email address : [EMAIL PROTECTED]
System Configuration
-
Architecture (example: Intel Pentium) : Intel Pentium
Operating System (example: Linux 2.0.26 ELF) : FreeBSD-4.2-STABLE
PostgreSQL ve
Tae, KwangHo ([EMAIL PROTECTED]) reports a bug with a severity of 3
The lower the number the more severe it is.
Short Description
7.0.3 max function
Long Description
create table aaa ( aa varchar(3) );
insert into aaa values ('001');
insert into aaa values ('002');
insert into aaa values ('003')
Marcin Kowalski <[EMAIL PROTECTED]> writes:
> Is it possible that one of the system tables has been corrupted and shows
> multiple entries for the tables?
Come to think of it, this is a fairly likely behavior if you have
multiple entries in pg_shadow with the same usesysid.
On Wed, Mar 28, 2001 at 08:30:39AM -0500, [EMAIL PROTECTED] wrote:
> Tae, KwangHo ([EMAIL PROTECTED]) reports a bug with a severity of 3
> The lower the number the more severe it is.
>
> Short Description
> 7.0.3 max function
>
> Long Description
> create table aaa ( aa varchar(3) );
> insert in
[EMAIL PROTECTED] writes:
> create table aaa ( aa varchar(3) );
> insert into aaa values ('001');
> insert into aaa values ('002');
> insert into aaa values ('003');
> select max(aa) from aaa;
> max
> -
> 002
> (1 row)
Hm. It works for me, and doubtless for most other people. Something
Hubert Hafner ([EMAIL PROTECTED]) reports a bug with a severity of 3
The lower the number the more severe it is.
Short Description
Datatype SERIAL incorrectly interpreted
Long Description
If you create a table with more than 1 SERIAL, only for the last a sequence is created
by PostgreSQL. The o
[EMAIL PROTECTED] writes:
> If you create a table with more than 1 SERIAL, only for the last a
> sequence is created by PostgreSQL. The other fields only set to
> INTEGER, but there is no sequence for.
This is fixed in 7.1.
regards, tom lane
---(e
Iván Baldo ([EMAIL PROTECTED]) reports a bug with a severity of 4
The lower the number the more severe it is.
Short Description
Option in pg_hba.conf to specify permissions and owner for the socket file
Long Description
It would be nice to have options in the pg_hba.conf file to specify the perm
