Re: NpgsqlCopySerializer blows up if no rows are saved

From: "Francisco Figueiredo Jr(dot)" <francisco(at)npgsql(dot)org>
To: AK <alkuzo(at)gmail(dot)com>
Cc: PgSql General <pgsql-general(at)postgresql(dot)org>
Subject: Re: NpgsqlCopySerializer blows up if no rows are saved
Date: 2013-12-03 02:50:03
Message-ID: CACUQdMbX2jZ_Gnd=R=2+0i8Mrd0wwLTU_vdUFd4MQW-0FoU8=g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Whooops. Sorry for not replying. :-(

I'll check the problem and reply you back.
Em 02/12/2013 20:21, "AK" <alkuzo(at)gmail(dot)com> escreveu:

> I did a week ago - and got no replies at all. Thank you.
>
>
>
> --
> View this message in context:
> http://postgresql.1045698.n5.nabble.com/NpgsqlCopySerializer-blows-up-if-no-rows-are-saved-tp5781300p5781316.html
> Sent from the PostgreSQL - general mailing list archive at Nabble.com.
>
>
> --
> 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
>

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Shuwn Yuan Tee 2013-12-03 10:32:02 Postgres 9.3 read block error went into recovery mode
Previous Message Bruce Momjian 2013-12-03 02:25:12 Re: Trust intermediate CA for client certificates