ead, find out that discussion thread
really has nothing to do with your topic of interest, repeat, finally try
something different, repeat? Again, my apologies for lighting a fire under
everyone.
Regards,
Steve K.
--
View this message in context:
http://postgresql.1045698.n5.nabble.com
a or not. Effectively these were silent failures.
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.
Regards,
Steve K.
--
View this message in context:
http://postgresq
te public embarassment. Maybe others will get something
too. It's how we all get ahead. At any rate, thanks for your time and I
look forward to what you find.
Steve K.
--
View this message in context:
http://postgresql.1045698.n5.nabble.com/PQputCopyData-dont-signal-error-tp4302
.
Thanks again for the suggestion and I'll definitely keep PGLoader in mind as
things unfold here on this project.
Best Regards,
Steve K.
--
View this message in context:
http://postgresql.1045698.n5.nabble.com/PQputCopyData-dont-signal-error-tp4302340p5798038.html
Sent from th
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 to a log so that
not all of it is lost.
Regards,
Steve K.
--
View this
gards to everyone and thank you all for your time,
Steve K.
--
View this message in context:
http://postgresql.1045698.n5.nabble.com/PQputCopyData-dont-signal-error-tp4302340p5798002.html
Sent from the PostgreSQL - hackers mailing list archive at Nabble.com.
--
Sent via pgsql-hackers
shutdowns etc...)
I haven't tried using inserts yet with multiple "values" clauses but have
read this is possible. However, once the planner gets involved, speed drops
noticeably.
Thanks to everyone for their time or any feedback.
Regards,
Steve K.
--
View this message in
