On 2012-10-12 11:30, Sergey Konoplev wrote:
On Fri, Oct 12, 2012 at 1:20 AM, Condor wrote:
Even without tel filed result and type of scan is the same (Seq
Scan).
This is because your table has to few rows and it is easier to seq
scan. Add more rows, eg. 100 000, then ANALYZE the table and run
On 10/14/12 6:37 PM, Alexander Gataric wrote:
On 10/14/12 5:52 PM, Alexander Gataric wrote:
>
> I'm on a project which requires adding PostgreSQL tables to DB2 >
Federated Server. I'm getting an error with PostgreSQL data types >
boolean, text, bytea, and XML. I believe this can be solved with
Hi
This is the output of meminfo when the system is under some stress.
Thanks
cif@ip-10-194-167-240:/tmp$ cat /proc/meminfo
MemTotal:7629508 kB
MemFree: 37820 kB
Buffers:2108 kB
Cached: 5500200 kB
SwapCached: 332 kB
Active: 4172020 kB
Inacti
On 10/15/2012 09:37 AM, Alexander Gataric wrote:
The IBM people aren't being helpful so I thought I'd ask here.
Try dba.stackexchange.com .
--
Craig Ringer
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/m
The IBM people aren't being helpful so I thought I'd ask here.
Sent from my smartphone
- Reply message -
From: "John R Pierce"
To:
Subject: [GENERAL] Mapping PostgreSQL data types to DB2 Federated Server
Date: Sun, Oct 14, 2012 8:05 pm
On 10/14/12 5:52 PM, Alexander Gataric wrote:
>
>
On 10/14/12 5:52 PM, Alexander Gataric wrote:
I'm on a project which requires adding PostgreSQL tables to DB2
Federated Server. I'm getting an error with PostgreSQL data types
boolean, text, bytea, and XML. I believe this can be solved with the
CREATE TYPE MAPPING in Fed Server. Does anyone k
Hello,
I'm on a project which requires adding PostgreSQL tables to DB2 Federated
Server. I'm getting an error with PostgreSQL data types boolean, text,
bytea, and XML. I believe this can be solved with the CREATE TYPE MAPPING in
Fed Server. Does anyone know which values to use? I'm not that famili
Hi
I've returned the memory configs to the default, erased data from my db and
am testing the system again.
This is the output of *cat /proc/meminfo*
Thanks
root@ip-10-194-167-240:~# cat /proc/meminfo
MemTotal:7629508 kB
MemFree: 170368 kB
Buffers: 10272 kB
Cached:
Arturo Pie Joa writes:
> I have found a strange behavior in postgreSQL when adding columns with
> defaults of a domain type in a schema different from public.
As the other respondent said, you're confusing the issue by using
conflicting names. If you hadn't done that, you'd see this:
regression
On Oct 14, 2012, at 15:49, Arturo Pie Joa wrote:
> Hello,
>
> I have found a strange behavior in postgreSQL when adding columns with
> defaults of a domain type in a schema different from public. This is the
> example to reproduce it:
>
> CREATE SCHEMA schema_1;
> CREATE DOMAIN schema_1.text
Hello,
I have found a strange behavior in postgreSQL when adding columns with defaults
of a domain type in a schema different from public. This is the example to
reproduce it:
CREATE SCHEMA schema_1;
CREATE DOMAIN schema_1.text AS text;
SET search_path TO schema_1, pg_catalog;
CREATE TABLE te
11 matches
Mail list logo
