-
-
Notifications
You must be signed in to change notification settings - Fork 530
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[patch] pgloader hangs on connection errors (python 2.4) #1
Comments
Here's a patch that fixes some of these problems:
Also, it would be nice if pgloader returned some well-defined (and documented) error codes to the OS, so calling scripts can check them, maybe something like:
Note that I don't really "know" python, please double check these changes... they seem to work for me though.
|
BTW is there a mailing list? This issue tracker doesn't support attachments. I had to add a tab to every line in the above patch to prevent it from being re-formatted. Am I doing this wrong? I have never used github (or git or python for that matter) before today, sorry. |
The github way seems to be: fork the project, use git, push your patches on your fork, then create a pull request ticket --- or just a ticket like this, I can see the patches in the Fork Queue tab too. I'd appreciate it if you can send me "real" patches, either this way to the plain git way (git send-email, then I git am -s) |
It turns out that when using *print-pretty* in CCL we then have CL reader references in the output, such as in the following example: QUERY: comment on table mysql.base64 is $#1=DXIDC_EMLAQ$Test decoding base64 documents$#1#$ Of course that's wrong, so prevent this from happening by forcing *print-pretty* to nil in a top-level function. We still turn this on in the monitor thread when printing error messages as those might contain recursive data structures.
Hi,
It seems that pgloader hangs after encountering many types of errors, e.g., database connection errors (but possibly other kinds of errors, too). It looks like it hangs after catching (and printing) the exception. I think it may have something to do with multi-threading.
Here's the output of of a sample invocation when the specified DB server is down:
At this point it hangs and ignores SIGINT (KeybpardInterrupt).
I'm using python 2.4, psycopg 2.0.13, libpq 8.1.21 on RedHat EL 5 (update 5).
Thanks,
D.
The text was updated successfully, but these errors were encountered: