Re: [BUGS] PostgreSQL BugTool Submission

2000-08-23 Thread Tom Lane
[EMAIL PROTECTED] writes: > The backend call lseek much more often than it has to. Denis Perchine fixed this a couple of months ago. You might care to repeat your experiments with current sources (see our CVS server, or the nightly snapshot tarball on our FTP server). If there's still a problem

[BUGS] PostgreSQL BugTool Submission

2000-08-23 Thread pgsql-bugs
Doug Mitchell ([EMAIL PROTECTED]) reports a bug with a severity of 3 The lower the number the more severe it is. Short Description Excessive seeking by backend Long Description The backend call lseek much more often than it has to. The storage manage should not do either of the following: 1.

Re: [BUGS] PostgreSQL BugTool Submission

2000-08-23 Thread Tom Lane
[EMAIL PROTECTED] writes: > When trying to list/describe ( \d ) > ERROR: getattproperties: no attribute tuple 1259 -2 Sounds pretty thoroughly hosed ... but there's not enough info here to diagnose the problem. Is this a fresh install, or an installation that had been working for a while and

Re: [BUGS] PostgreSQL BugTool Submission

2000-08-23 Thread Stephan Szabo
Yes, this is a known issue due to the fact that the triggers use SPI and need to use SELECT ... FOR UPDATE to lock the rows it is reading (and select for update requires the update permission). The workaround I know about for now is to give update permission and make triggers to disallow updates

[BUGS] PostgreSQL BugTool Submission

2000-08-23 Thread pgsql-bugs
chris vale ([EMAIL PROTECTED]) reports a bug with a severity of 2 The lower the number the more severe it is. Short Description psql list ( \d ) command returns error Long Description Using 7.0.2 on LinuxPPC (YellowDog ) and RPMS's from postgresql.org. When trying to list/describe ( \d ) ERR

Re: [BUGS] PostgreSQL BugTool Submission

2000-08-23 Thread Tom Lane
[EMAIL PROTECTED] writes: > When performing a query against a table that has a 64bit (int8) > primary key a sequential scan always takes place. Possibly a casting issue. Observe: regression=# create table foo1 (f1 int8 primary key); NOTICE: CREATE TABLE/PRIMARY KEY will create implicit index '

[BUGS] PostgreSQL BugTool Submission

2000-08-23 Thread pgsql-bugs
() reports a bug with a severity of 2 The lower the number the more severe it is. Short Description Your bug system shows misformatted bug description and 'example code' Long Description When you show long description of the bug tag should be used in order to show text as it was entered Samp

[BUGS] PostgreSQL BugTool Submission

2000-08-23 Thread pgsql-bugs
Stu Coates ([EMAIL PROTECTED]) reports a bug with a severity of 2 The lower the number the more severe it is. Short Description Not performing index scan for 64bit primary Long Description When performing a query against a table that has a 64bit (int8) primary key a sequential scan always takes

[BUGS] PostgreSQL BugTool Submission

2000-08-23 Thread pgsql-bugs
NAGY Andras ([EMAIL PROTECTED]) reports a bug with a severity of 3 The lower the number the more severe it is. Short Description Foreign keys referencing read-only tables fail Long Description Consider two tables, foo(barid) and bar(id, str), where foo has a foreign key referencing bar(id). It

[BUGS] PostgreSQL BugTool Submission

2000-08-23 Thread pgsql-bugs
Gregg Wonderly ([EMAIL PROTECTED]) reports a bug with a severity of 1 The lower the number the more severe it is. Short Description JDBC driver broken for ResultSet.getTimeStamp() Long Description The JDBC driver in 7.0.2 uses Timestamp.toString() to create the string representation of the time

[BUGS] PostgreSQL BugTool Submission

2000-08-23 Thread pgsql-bugs
Mickael FEYS ([EMAIL PROTECTED]) reports a bug with a severity of 2 The lower the number the more severe it is. Short Description Unexpected behaviour of the ecpg -D option. Long Description Configuration : system : sun sparc ultra 5 os : solaris 2.7 postgres : 7.0.2 compilator : cc com