Re: URGENT: temporary table not recognized?

From: Phoenix Kiula <phoenix(dot)kiula(at)gmail(dot)com>
To: Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com>
Cc: Steve Crawford <scrawford(at)pinpointresearch(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PG-General Mailing List <pgsql-general(at)postgresql(dot)org>
Subject: Re: URGENT: temporary table not recognized?
Date: 2012-01-07 01:33:00
Message-ID: CAFWfU=uDjvikDWX4yaBMiVtv92QHJUwvyxnsKdAHu24ybJ_GDw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Fri, Jan 6, 2012 at 8:19 PM, Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com> wrote:
> On Friday, January 06, 2012 4:16:09 pm Phoenix Kiula wrote:
>> On Fri, Jan 6, 2012 at 6:54 PM, Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com> wrote:
>> > Try:
>> > copy vl from 'data.txt' WITH CSV DELIMITER '|';
>>
>> Doesn't work. Can't see what the different in CSV is from a text file.
>> Same errors are thrown.
>>
>> > If that doesn't work take a look at pgloader:
>> > http://pgfoundry.org/projects/pgloader/
>>
>> Wow, another geeky tool. Hard to find documentation. Archaic
>> presentation, no simple steps to install and get using. Anyway doesn't
>> seem to provide the options I need
>> (http://pgloader.projects.postgresql.org/) --
>
> Install:
> Download
> tar -xzvf pgloader-2.3.2.tar.gz
> cd pgloader-2.3.2/
> sudo make
>
> Very difficult.
>
> http://pgloader.projects.postgresql.org/

Sorry. That I already did.

But where's the config file? How to configure the config file?
Where's the simple doc (not on that ugly PGFoundry website, I mean in
English that people can understand what to do, with a starting
sample?)

>> a) Ability to assign more than one NULL value
...

So Null, or Empty Value? (I will ignore the Phd I need for all that
geeky "reformat" jazz)

My request is simple. If a value is missing, ignore the line and move
on. This is an option that's perfectly alright to expect/need. I know
PG is being super-disciplined and strict, which is great if that's the
default, but to remove any option of flexibility on this pretext is a
little silly. And sounds like an excuse.

>> b) Ability to ignore lines altogether that have any problem
>
> reject_log
> In case of errors processing input data, a human readable log per rejected input
> data line is produced into the reject_log file.
> reject_data
> In case of errors processing input data, the rejected input line is appended to
> the reject_data file.

I don't need a reject log if the main command will croak and be
utterly useless, as COPY is already. If the full command will go but
some lines will be ignored then a reject log is useful so I can
identify the ignored lines. Which is it? My sense is it's the former,
which means this entire software is just a more complicated way of
(non-)achieving the same thing I do with COPY.

> I await with bated breath your most excellent patch to COPY.

Thanks for your help on this list. I'll be moving to more modern
couchDB type databases eventually anyway, but for now I'm stuck with
PG.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message John R Pierce 2012-01-07 03:38:30 Re: URGENT: temporary table not recognized?
Previous Message Adrian Klaver 2012-01-07 01:19:48 Re: URGENT: temporary table not recognized?