Re: [pmacct-discussion] pgsql debug messages incomplete

2014-08-04 Thread Karl O. Pinc
On 08/04/2014 03:10:16 AM, Janos Lehnhardt wrote: > hi, could anyone tell me how to unsuscribe of this list? :) thanks in > advance! You read all the way to the bottom of the email, go to the supplied URL, and follow the instructions there. Karl Free Software: "You don't pay back, you pay fo

Re: [pmacct-discussion] pgsql debug messages incomplete

2014-08-04 Thread Janos Lehnhardt
hi, could anyone tell me how to unsuscribe of this list? :) thanks in advance! On 23.07.2014 19:30, Paolo Lucente wrote: Hi Pat, Thanks for the feedback. Yes, that behaviour of the wiki is expected and documented on the main page: "Anyone may read these pages. In order to add or edit content a

Re: [pmacct-discussion] pgsql debug messages incomplete

2014-07-23 Thread Paolo Lucente
Hi Pat, Thanks for the feedback. Yes, that behaviour of the wiki is expected and documented on the main page: "Anyone may read these pages. In order to add or edit content a registration is required. Registration is manual process, needs some motivation and can be submitted to the author of pmacc

Re: [pmacct-discussion] pgsql debug messages incomplete

2014-07-23 Thread THE MIGHTY VEXORG
"Nice to have" is a good description of this problem. I think documenting this behavior on the pmacct wiki page for sql_use_copy would be good enough for me. I tried to create an account on the wiki in preparation to add to the documentation but when I try to create a new account I get the error "U

Re: [pmacct-discussion] pgsql debug messages incomplete

2014-07-23 Thread Paolo Lucente
Hi Pat, You are right: COPY operation, or more formally PQputCopyData() of the PostgreSQL API, returns error only for transmission issues and not for parsing ones. This is documented on a recent pretty heated thread on the pgsql-hackers mailing-list (to me, the following is the key message of that