I don't know what SQL2008 says about SUBSTRING, but SQL2003 says in
ISO/IEC 9075-2:2003 (E), 6.29 , General Rules,
5), page 261:
d) If R [the regular expression] does not contain exactly two
occurrences of the two-character sequence consisting of E [the escape
character], each immediately fol
The following bug has been logged online:
Bug reference: 5257
Logged by: Roman Kononov
Email address: kono...@ftml.net
PostgreSQL version: 8.4.2
Operating system: GNU/Linux x86_64
Description:wrong results of SUBSTRING with SQL regular expressions
Details:
test
The bitfromint8() and bitfromint4() are hosed. They produce wrong
results when the BIT size is more than 64 and 32 respectively, and the
BIT size is not multiple of 8, and the most significant byte of the
integer value is not 0x00 or 0xff.
For example:
test=# select (11::int4<<23 | 11::int4):
The following bug has been logged online:
Bug reference: 5237
Logged by: Roman Kononov
Email address: kono...@ftml.net
PostgreSQL version: 8.4.1
Operating system: GNU/Linux x86_64
Description:strange int->bit and bit->int conversions
Details:
test=# sele
The following bug has been logged online:
Bug reference: 4926
Logged by: Roman Kononov
Email address: kono...@ftml.net
PostgreSQL version: 8.4.0
Operating system: Linux x86_64
Description:too few pathkeys for mergeclauses
Details:
test=# create table junk(i int
On 2009-04-03 23:32 Tom Lane said the following:
Roman Kononov writes:
On 2009-04-03 14:57 Tom Lane said the following:
I think we could fix this by having interval_hash() duplicate the
total-span calculation done by interval_cmp_internal, and then return
the hash of the resulting TimeOffset
On 2009-04-03 14:57 Tom Lane said the following:
I think we could fix this by having interval_hash() duplicate the
total-span calculation done by interval_cmp_internal, and then return
the hash of the resulting TimeOffset. This is going to break existing
hash indexes on intervals, but there seem
The following bug has been logged online:
Bug reference: 4748
Logged by: Roman Kononov
Email address: kono...@ftml.net
PostgreSQL version: 8.3.7
Operating system: GNU/Linux x86_64
Description:hash join and sort-merge join make different results
Details:
test-std
On 2009-03-28 11:34 Tom Lane said the following:
If you have an actual use-case for this, what do you think it should do?
I don't have a use-case (other than hypothetical "how many more years
and quarters did it take to complete this particular software project
than that particular project").
The following bug has been logged online:
Bug reference: 4739
Logged by: Roman Kononov
Email address: kono...@ftml.net
PostgreSQL version: 8.3.7
Operating system: GNU/Linux x86_64
Description:strange behavior of EXTRACT(quarter from INTERVAL)
Details:
test=# select
The following bug has been logged online:
Bug reference: 4718
Logged by: Roman Kononov
Email address: kono...@ftml.net
PostgreSQL version: 8.3.7
Operating system: GNU/Linux x86_64
Description:"select +'8:00'::interval;" gives an error
Details:
The following bug has been logged online:
Bug reference: 4702
Logged by: Roman Kononov
Email address: kono...@ftml.net
PostgreSQL version: 8.3.6 and older
Operating system: GNU/Linux x86_64
Description:refusal to compute date_trunc('week', '0001-12-0
The following bug has been logged online:
Bug reference: 4114
Logged by: Roman Kononov
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.3.1
Operating system: x86_64 GNU/Linux
Description:Inconsistent shift operator
Details:
The below test cases show the
The below test cases show the obvious inconsistency between different
integer types.
Regards,
Roman
test=# \t
Showing only tuples.
test=# select 1::int2 << 17;
0
test=# select 1::int4 << 33;
2
test=# select 1::int8 << 65;
2
test=# select 2::int2 >> 17;
0
tes
The following bug has been logged online:
Bug reference: 2846
Logged by: Roman Kononov
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2.0 and older
Operating system: linux 2.6.15-27-amd64 ubuntu
Description:inconsistent and confusing handling of underflows
15 matches
Mail list logo
