The following bug has been logged online:
Bug reference: 2197
Logged by: Sunil Basu
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.0
Operating system: Windows 2000 Server
Description:PostgreSQL error- 'could not read block 0 of relation'
Details:
I am runnin
Tom Lane writes:
> "Jaime Casanova" <[EMAIL PROTECTED]> writes:
>> in my machine (win xp) i was trying to start psql (8.1.1) with
>> log_min_messages to debug5 (just to see the messages :) but even the
>> service start i cannot use psql nor pgadmin i receive an error of
>> server closed the connec
The following bug has been logged online:
Bug reference: 2196
Logged by:
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.2
Operating system: alphaev68-dec-osf5.1a
Description:Useless RECHECK on RTREE index
Details:
create table tpoints (x int, y int);
CREA
The following bug has been logged online:
Bug reference: 2198
Logged by: Jacques Gollion
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.2
Operating system: Windows 2000
Description:Now returns always same date and time during a session
Details:
The followi
The following bug has been logged online:
Bug reference: 2203
Logged by: Robert Hostetter
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1
Operating system: CentOS 4.1
Description:Group by, suggested "feature"
Details:
I'm sure this will be considered a miss
"" <[EMAIL PROTECTED]> writes:
> Bitmap Heap Scan on tpoints (cost=1.05..10.46 rows=10 width=8)
>Recheck Cond: ('(1,1),(0,0)'::box && box(point((x)::double precision,
> (y)::double precision), point((x)::double precision, (y)::double
> precision)))
>-> Bitmap Index Scan on i_tpoints (co
"Jacques Gollion" <[EMAIL PROTECTED]> writes:
> The following functions returns the first time the right date and time but
> when called at several date and time returns the date that was returned at
> the first call.
Please read
http://www.postgresql.org/docs/8.1/static/functions-datetime.html#FU
On Mon, Jan 23, 2006 at 11:40:43AM +, Jacques Gollion wrote:
> The following functions returns the first time the right date and time but
> when called at several date and time returns the date that was returned at
> the first call.
See "Current Date/Time" in the documentation:
http://www.pos
Robert Hostetter wrote:
> If you group by a primary key for a table,
> you still have to include all the other columns you SELECT from that
> row, even though its guaranteed uniuqe because its a primary key.
Yes, this feature request is known as supporting functional
dependencies. We're aware of
On Tue, 2006-01-17 at 22:00 +, Daniel Afonso Heisler wrote:
> But, when i run the next query, it don't return TRUE
> # SELECT true WHERE 1 NOT IN (2,NULL,3);
These are not bugs.
The first statement is equivalent to
# select true where (1 != 2) and (1 != NULL) and (1 != 3);
1 != NULL is it
10 matches
Mail list logo
