"Maxim Boguk" writes:
> I found that strange effect while helping with slow query on russian
> postgresql online forum.
Please try to put together a self-contained test case for this.
I could not reproduce such a weird result here, but that probably
just means there's something strange about your
On 01/02/11 15:20, Alexandre wrote:
The following bug has been logged online:
Bug reference: 5859
Logged by: Alexandre
Email address: ultr...@gmail.com
PostgreSQL version: 8.4.7
Operating system: Windows 7
Description:XML result in line and column
Details:
The name
The following bug has been logged online:
Bug reference: 5885
Logged by: Maxim Boguk
Email address: maxim.bo...@gmail.com
PostgreSQL version: 8.4.4
Operating system: Linux
Description:Strange rows estimation for left join
Details:
I found that strange effect while h
2011/2/14 Kevin Grittner :
> Pavel Stehule wrote:
>
>> p.s. Using a case sensitive identifiers isn't good idea
>
> Is there any reason for that assertion besides the need to
> consistently quote them?
>
readability - and when you are started quoting, then you have to use
quotes everywhere.
Reada
"" writes:
> When creating a server-side C function, things go wrong when I (in the same
> function) return some results via SPI_returntuple, and other results by
> manually creating HeapTuples. This applies even if the source for both
> returns are the same data in the same table.
I think the p
Pavel Stehule wrote:
> p.s. Using a case sensitive identifiers isn't good idea
Is there any reason for that assertion besides the need to
consistently quote them?
-Kevin
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgre
Hello
2011/2/14 yashar ebrahimpoor :
>
> The following bug has been logged online:
>
> Bug reference: 5884
> Logged by: yashar ebrahimpoor
> Email address: ebrahimpoor.yas...@gmail.com
> PostgreSQL version: 8.4.7
> Operating system: centos 5.5
> Description: i cant sele
The following bug has been logged online:
Bug reference: 5884
Logged by: yashar ebrahimpoor
Email address: ebrahimpoor.yas...@gmail.com
PostgreSQL version: 8.4.7
Operating system: centos 5.5
Description:i cant select entire array values
Details:
CREATE TABLE "flight
dba wrote:
I wanted to create index 0f 3 numeric array. But it is allowing to insert
more than 4 elements
CREATE TABLE abs(no int[3]);
CREATE TABLE
zivah=# INSERT INTO abs VALUES('{1,3,34,343,4342342,342}');
INSERT 0 1
I need a solution to store an elements exactly 3. More than 3 should not
On Mon, Feb 14, 2011 at 5:21 PM, dba wrote:
>
>
> I wanted to create index 0f 3 numeric array. But it is allowing to insert
> more than 4 elements
>
> CREATE TABLE abs(no int[3]);
> CREATE TABLE
>
> zivah=# INSERT INTO abs VALUES('{1,3,34,343,4342342,342}');
> INSERT 0 1
>
> I need a solution to
I wanted to create index 0f 3 numeric array. But it is allowing to insert
more than 4 elements
CREATE TABLE abs(no int[3]);
CREATE TABLE
zivah=# INSERT INTO abs VALUES('{1,3,34,343,4342342,342}');
INSERT 0 1
I need a solution to store an elements exactly 3. More than 3 should not be
allowed.
The following bug has been logged online:
Bug reference: 5883
Logged by:
Email address: vegard.bo...@met.no
PostgreSQL version: 8.4.7
Operating system: ubuntu lucid
Description:Error when mixing SPI_returntuple with returning regular
HeapTuple
Details:
When creatin
12 matches
Mail list logo
