Re: [HACKERS] PQputCopyData dont signal error

Martijn van Oosterhout writes: > To move the conversation along: > https://github.com/postgres/postgres/blob/master/src/bin/psql/copy.c#L664 > Seems possibly even more robust than most people will code, but it's > had a lot of real world testing. Note that the looping behavior there is actually

Re: [HACKERS] PQputCopyData dont signal error

On Tue, Apr 01, 2014 at 01:53:13PM -0400, Robert Haas wrote: > > One of the things you mentioned is "I often find it necessary to refer to > > existing examples of code when trying to figure out how to do things > > correctly". I couldn't agree more. Haven't seen one yet, but found plenty > > of

Re: [HACKERS] PQputCopyData dont signal error

On Tue, Apr 1, 2014 at 12:14 PM, steve k wrote: > I'm already there. Obviously I'm the only one in the room that didn't get > the memo. I've had some time to reflect on what might be done differently, > just not any time to try it. If I get it to work I'll let everyone know. > The code I was wo

Re: [HACKERS] PQputCopyData dont signal error

Thanks Robert, I'm already there. Obviously I'm the only one in the room that didn't get the memo. I've had some time to reflect on what might be done differently, just not any time to try it. If I get it to work I'll let everyone know. The code I was working with went away when the Network a

Re: [HACKERS] PQputCopyData dont signal error

On Mon, Mar 31, 2014 at 4:21 PM, steve k wrote: > I'd love to see an actual working example where an executing C++ program was > able to in fact determine that copy data containing bad data that was sent > by the C++ program was rejected by the server and subsequently the C++ > program was able to

Re: [HACKERS] PQputCopyData dont signal error

On Tue, Apr 1, 2014 at 1:33 AM, Alvaro Herrera wrote: > steve k wrote: > >> I am examining other ways to do mass inserts/writes that allow for >> notification if some of the data contained within for some reason fails to >> copy/insert so that the cause of the bad data can be examined and remedied

Re: [HACKERS] PQputCopyData dont signal error

steve k wrote > Sorry I can't provide more information but I do appreciate your time. If > you can't get any further with it I understand and don't expect another > reply. For the benefit of others I'm reading this as basically you've found a better way to do this so you are no longer concerned

Re: [HACKERS] PQputCopyData dont signal error

David, The code I posted is what I started/finished with. As I tried to figure things out I kept adding PQgetResult, PQresultStatus and PQresultErrorMessage calls and writing the results to the log file. By the time I was done it was so messy that I stripped all that messaging/logging back out

Re: [HACKERS] PQputCopyData dont signal error

steve k wrote > I started with this: > DBInsert_excerpts6_test_cpdlc.cpp > > > Can you point out to me where in that code you've followed this instruction from the documentation: "After successfully ca

Re: [HACKERS] PQputCopyData dont signal error

I started with this: DBInsert_excerpts6_test_cpdlc.cpp Due to a cut and paste error I was originally querying the wrong sequence which led to me wondering why data wasn't in the table that the log repor

Re: [HACKERS] PQputCopyData dont signal error

Hi Alvaro, Thanks for the prompt response. PGLoader looks like an awesome project and I especially liked this part: /"Handling PostgreSQL errors Some data will get rejected by PostgreSQL, even after being carefully prepared by the transformation functions you can attach to pgloader. Then pgl

Re: [HACKERS] PQputCopyData dont signal error

steve k wrote > Am I to understand then that I should expect no error feedback if copy > fails because of something like attempting to insert alphabetic into a > numeric? > > I apologize for my ignorance, but all my return codes were always > successful (PGRES_COMMAND_OK) even if nothing was cop

Re: [HACKERS] PQputCopyData dont signal error

steve k wrote: > I am examining other ways to do mass inserts/writes that allow for > notification if some of the data contained within for some reason fails to > copy/insert so that the cause of the bad data can be examined and remedied > as soon as it occurs as well as writing the offending data

Re: [HACKERS] PQputCopyData dont signal error

Am I to understand then that I should expect no error feedback if copy fails because of something like attempting to insert alphabetic into a numeric? I apologize for my ignorance, but all my return codes were always successful (PGRES_COMMAND_OK) even if nothing was copied due to garbage data.

Re: [HACKERS] PQputCopyData dont signal error

On 03/31/2014 10:18 AM, steve k wrote: These were my results: I'd advise anyone contemplating using this feature to seriously s

Re: [HACKERS] PQputCopyData dont signal error

These were my results: I'd advise anyone contemplating using this feature to seriously seriously seriously test this and exam

Re: [HACKERS] PQputCopyData dont signal error

steve k wrote > I realize this is an old thread, but seems to be the only discussion I can > find on this topic "I have a problem with PQputCopyData function. It > doesn't signal some error. " > > I am using from within a c++ program: > PQexec(m_pConn, "COPY... ...FROM stdin"), > >

Re: [HACKERS] PQputCopyData dont signal error

steve k writes: > I realize this is an old thread, but seems to be the only discussion I can > find on this topic "I have a problem with PQputCopyData function. It doesn't > signal some error. " PQputCopyData/PQputCopyEnd are only concerned with transferring data. After you're done with that, y

Re: [HACKERS] PQputCopyData dont signal error

I realize this is an old thread, but seems to be the only discussion I can find on this topic "I have a problem with PQputCopyData function. It doesn't signal some error. " I am using from within a c++ program: PQexec(m_pConn, "COPY... ...FROM stdin"), followed by PQputCopyData(m_p

Re: [HACKERS] PQputCopyData dont signal error

Jeff Davis writes: > On Thu, 2011-04-14 at 10:50 +0300, Heikki Linnakangas wrote: >> I think you'll need to send all the data and finish the COPY until you >> get an error. If you have a lot of data to send, you might want to slice >> it into multiple COPY statements of say 50MB each, so that yo

Re: [HACKERS] PQputCopyData dont signal error

On Thu, 2011-04-14 at 10:50 +0300, Heikki Linnakangas wrote: > On 14.04.2011 10:15, Pavel Stehule wrote: > > Hello > > > > I have a problem with PQputCopyData function. It doesn't signal some error. > > > > while ((row = mysql_fetch_row(res)) != NULL) > > { > >

Re: [HACKERS] PQputCopyData dont signal error

On 14.04.2011 10:15, Pavel Stehule wrote: Hello I have a problem with PQputCopyData function. It doesn't signal some error. while ((row = mysql_fetch_row(res)) != NULL) { snprintf(buffer, sizeof(buffer), "%s%s\n", row[0], row[1]);

Re: [HACKERS] PQputCopyData dont signal error

Hello > > The way COPY works is that PQputCopyData just sends the data to the server, > and the server will buffer it in its internal buffer and processes it when > it feels like it. The PQputCopyData() calls don't even need to match line > boundaries. > Yes, it is current behave - then document

[HACKERS] PQputCopyData dont signal error

Hello I have a problem with PQputCopyData function. It doesn't signal some error. while ((row = mysql_fetch_row(res)) != NULL) { snprintf(buffer, sizeof(buffer), "%s%s\n", row[0], row[1]); copy_result = PQputCopyData