The following bug has been logged online:
Bug reference: 2392
Logged by: Raphael Jacquot
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.3
Operating system: Linux Gentoo 2006.0
Description:Feature request : point_ops
Details:
I have the following table:
CR
The following bug has been logged online:
Bug reference: 2394
Logged by: Alexander Kirpa
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.3
Operating system: FreeBSD 6.0
Description:Multiple TRUNCATE within transaction
Details:
Within one transaction each 'T
The following bug has been logged online:
Bug reference: 2395
Logged by: wangshj
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.3
Operating system: CentOS release 4.3 (Final)
Description:Can't get right type oid by PQftype.
Details:
I create a domain type
The following bug has been logged online:
Bug reference: 2396
Logged by: Martin
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.3
Operating system: Win XP SP 2 German
Description:SELECT to_number('6500', '999,999.99') != 650
Details:
1.) I have found some m
The following bug has been logged online:
Bug reference: 2397
Logged by: Péter Szabó
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.3
Operating system: Linux
Description:1 = SELECT ASCII(CHR(257))
Details:
Hi!
I have a Unicode-enabled PostgreSQL with th
The following bug has been logged online:
Bug reference: 2393
Logged by: Laurence Dawson
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.3
Operating system: Ubuntu Dapper Drake
Description:update fails with unique constraint violation
Details:
Here is the t
Laurence,that error is correct:CREATE TABLE test.test( a int4 NOT NULL DEFAULT nextval('
test.test_a_seq'::regclass), CONSTRAINT pk PRIMARY KEY (a))WITHOUT OIDS;And then try an update:lstore=> select * from test.test; a 1 2 3 4 5 6 7 8
9 10lstore=> update test.test set a = a + 2 whe
Isn't that expected? Your query will try to update row 3 first and set
the primary key to 5, which in fact would violate the primary key
constraint on that table.
Laurence Dawson wrote:
And then try an update:
lstore=> select * from test.test;
a
1
2
3
4
5
6
7
8
9
10
(1
T.J. Ferraro wrote:
> Isn't that expected? Your query will try to update row 3 first and set
> the primary key to 5, which in fact would violate the primary key
> constraint on that table.
While the error is expected, it isn't valid based on the SQL spec. The
spec requires checks to happen at s
On Apr 14 06:30, wangshj wrote:
> In my database,the type oid of testdomainoid is 16385. But PQftype return 23
> for testdomainoid's type oid.
PQftype() returns the OID of the actual _type_ used in the domain.
Therefore, you get 23, OID of the int4/int type, in the above query.
> How could I get
"Alexander Kirpa" <[EMAIL PROTECTED]> writes:
> In case of many truncate (10-100 thousands or more) within one transaction,
> postgres receive serious performance problem for current operation (create
Why in the world are you doing that, and why do you think we need to
optimize that case? We don'
Volkan YAZICI <[EMAIL PROTECTED]> writes:
> On Apr 14 06:30, wangshj wrote:
>> In my database,the type oid of testdomainoid is 16385. But PQftype return 23
>> for testdomainoid's type oid.
> PQftype() returns the OID of the actual _type_ used in the domain.
> Therefore, you get 23, OID of the int4
12 matches
Mail list logo
