Hello,
I'm trying to import a text file into a table using the COPY command.
The text file contains four columns: id, col_1, col_2, col_3 (in that order).
My target table only has id and col_1.
From the documentation I assumed that the following statement
copy foo (id, col_1)
from
On 11/11/2012 05:33 PM, Thomas Kellerer wrote:
Hello,
I'm trying to import a text file into a table using the COPY command.
The text file contains four columns: id, col_1, col_2, col_3 (in that
order).
My target table only has id and col_1.
From the documentation I assumed that the
Craig Ringer wrote on 11.11.2012 11:23:
It seems like you want to be able to say something like this (imaginary)
syntax:
\copy test_copy (id, col1) FROM 'test.csv' CSV COLUMNS(1,2,IGNORE)
or some similar way to provide a column mapping from the CSV columns to
the output of the COPY command.
Hello all,
GoldenGate added PostgreSQL as a target database for replication. I tried
setting it up, and not finding any tutorial, put together a how to here -
http://jayadevanm.wordpress.com/2012/11/07/goldengate-replication-from-oracle-to-postgresql/
I think near real-time replication might have
Hi Laurenz:
Thank you for your kind reply.
Please let me dig it a little more:
I think that when a session is accessing a postgersql table. It will be
influenced by the followings:
Really old data (needed to be vacuumed, eg: old image at one day ago).
Recent data (committed and
Hi all：
I made partition tables:
postgres=# create table ptest(id integer, name varchar(20));
CREATE TABLE
postgres=# create table ctest01(CHECK(id500)) inherits (ptest);
CREATE TABLE
postgres=# create table ctest02(CHECK(id=500)) inherits (ptest);
CREATE TABLE
postgres=#
postgres=#
On 11/12/2012 10:39 AM, 高健 wrote:
The selection used where condition for every partition table, which
is not what I want. my rule is just for id column value.
Is `constraint_exclusion` turned on?
http://www.postgresql.org/docs/current/static/ddl-partitioning.html
On 11/12/2012 10:39 AM, 高健 wrote:
The selection used where condition for every partition table, which
is not what I want. my rule is just for id column value.
And my select sql statement's where condition is also for id column value.
After re-reading your question I see what you're getting at.
On 11/09/2012 05:26 PM, Steve Crawford wrote:
Bloat in pg_attribute would correlate with A) (or any constant
creation/destruction of tables). You can vacuum and/or reindex the
system tables if you are connected as the superuser but you are better
off preventing bloat by appropriate adjustment
Hi Craig:
Thank you for your reply.
I checked for constratint_exclusion , in my sample, on and partition is
same(I have no data on parent table). it really works for me.
I tried and found that constraint_exclusion can work in simple ways , but
not for complicated conditions such as id=a or id=b.
Hello,
I've installed unaccent on the public schema using CREATE EXTENSION.
However I have multiple schemas and they don't have the public schema on
their search path. I've tried calling public.unaccent() but it fails with
'text search dictionary unaccent does not exist'. I suppose it is trying
On 11/12/2012 02:24 PM, 高健 wrote:
Hi Craig:
Thank you for your reply.
I checked for constratint_exclusion , in my sample, on and partition
is same(I have no data on parent table). it really works for me.
I tried and found that constraint_exclusion can work in simple ways ,
but not for
12 matches
Mail list logo
