Re: Cannot import logs from csv

Your welcome;

Best wishes for fixes =)

Cheers,

Rémi-C

2013/10/18 Helen Griffiths <helen(dot)griffiths(at)durham(dot)ac(dot)uk>

> On Fri, 18 Oct 2013, Adrian Klaver wrote:
>
> This came up before recently in this thread:
>>
>> http://www.postgresql.org/**message-id/**CADK3HHJNEWKD9gNyXmjv9ABbn+**
>> 37rY3Mvp9=1j7msg9YpoBBBw(at)mail(dot)**gmail(dot)com<http://www.postgresql.org/message-id/CADK3HHJNEWKD9gNyXmjv9ABbn+37rY3Mvp9=1j7msg9YpoBBBw@mail.gmail.com>
>>
>> To cut to the chase, in that case the OP found:
>>
>> "Ok, I found the offending line. It was not the pgadmin line. There was a
>> line with a large binary insert."
>>
>> Not sure if that helps.
>>
>
> It might: there are then some lines like:
> 2013-10-11 02:44:26.164 BST,"postgres","course_**records",19216,"[local]",
> **525740b3.4b10,124887,"idle in transaction",2013-10-11 01:05:07
> BST,7/16388,0,LOG,00000,"**fastpath function call: ""loread"" (OID
> 954)",,,,,,,,
>
> I suspect the ""loread"" is the offender.
>
> Thanks to all for the help. I would never have thought to suspect the
> lines after the one given in the error message.
>
> --
> Helen Griffiths
>
>
>
> --
> Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/**mailpref/pgsql-general<http://www.postgresql.org/mailpref/pgsql-general>
>