You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for contributing to pgloader by reporting an
issue! Reporting an issue is the only way we can solve problems, fix bugs,
and improve both the software and its user experience in general.
The best bug reports follow those 3 simple steps:
show what you did,
show the result you got,
explain how the result is not what you expected.
In the case of pgloader, here's the information I will need to read in your
bug report. Having all of this is a big help, and often means the bug you
reported can be fixed very efficiently as soon as I get to it.
Please provide the following information:
pgloader --version
pgloader version "3.6.2~devel"
compiled with SBCL 1.4.7-1.6-suse
```
did you test a fresh compile from the source tree?
yes
did you search for other similar issues?
yes
how can I reproduce the bug?
I am running the command as given below using a shell script file.
issue-1 : If during migration, connection is interrupted for mysql server( i.e. rcmysql stop). It exits but the return status is zero, which is considered as success in shell-commands. It should return non-zero exit status.
issue-2 : If during migration,network is interrupted for mysql server(i.e.ifdown eth0). The pgloader process hangs forever and it will not exit. But if I do the same with target db that is postgres then it exits with non-zero exit status after 20 mins(more or less). It would be better if we do the same for mysql.
--
-- EDIT THIS FILE TO MATCH YOUR BUG REPORT
--
LOAD DATABASE
from mysql://filr:novell@<mysql-server-IP>:3306/srcDBname
into postgresql://g@@2:n@<postgressql-server-ip>:5432/tgtDBWthSplChr@2
ALTER SCHEMA 'srcDBname' RENAME TO 'public'
WITH create no tables
EXCLUDING TABLE NAMES MATCHING 'table1', 'table2', 'table3';
- [ ] pgloader output you obtain
for issue 1 - output :
2019-03-20T12:11:56.131000Z ERROR mysql: Failed to connect to mysql at "" (port 3306) as user "filr": Condition USOCKET:HOST-UNREACHABLE-ERROR was
for issue -2 : No Output . Pgloader hangs forever, we have to manually kill the process.
- [ ] data that is being loaded, if relevant
PASTE HERE THE DATA THAT HAS BEEN LOADED
- [ ] How the data is different from what you expected, if relevant
The text was updated successfully, but these errors were encountered:
Thanks for contributing to pgloader by reporting an
issue! Reporting an issue is the only way we can solve problems, fix bugs,
and improve both the software and its user experience in general.
The best bug reports follow those 3 simple steps:
In the case of pgloader, here's the information I will need to read in your
bug report. Having all of this is a big help, and often means the bug you
reported can be fixed very efficiently as soon as I get to it.
Please provide the following information:
pgloader --version
pgloader version "3.6.2~devel"
compiled with SBCL 1.4.7-1.6-suse
```
yes
did you search for other similar issues?
yes
how can I reproduce the bug?
I am running the command as given below using a shell script file.
issue-1 : If during migration, connection is interrupted for mysql server( i.e. rcmysql stop). It exits but the return status is zero, which is considered as success in shell-commands. It should return non-zero exit status.
issue-2 : If during migration,network is interrupted for mysql server(i.e.ifdown eth0). The pgloader process hangs forever and it will not exit. But if I do the same with target db that is postgres then it exits with non-zero exit status after 20 mins(more or less). It would be better if we do the same for mysql.
for issue 1 - output :
2019-03-20T12:11:56.131000Z ERROR mysql: Failed to connect to mysql at "" (port 3306) as user "filr": Condition USOCKET:HOST-UNREACHABLE-ERROR was
for issue -2 : No Output . Pgloader hangs forever, we have to manually kill the process.
PASTE HERE THE DATA THAT HAS BEEN LOADED
The text was updated successfully, but these errors were encountered: