Does nothing and shows no output

[PandaWood]

This command creates no table, no log, no errors, no nothing. Any obvious reason why?
(I have confirmed the exe is valid by first running --help and that works fine)
pgfutter_windows_amd64.exe --host "machine-766" --pass "postgres" --table "quick-table" csv "quick-table.csv"

[jsnet-ops]

Are you sure the settings are correct? pgfutter hardly returns postgres errors.
You can consult the postgres logging.

[mission-lblaney]

I'm having same issue connecting from Amazonlinux 2 to a postgress cluster. I run a similar command as OP and I get no output of any kind. then when I connect with psql I dont see a table created.

[LaurensBosscher]

This is a common issue with PGFutter and one that we all run into, at some point, there's a PR open since 2019 to improve the handling of errors: https://github.com/lukasmartinelli/pgfutter/pull/67/files but it doesn't look like this situation will change anytime soon.

My recommendation would be to try trail and error, check your postgress logging and look for alternatives for production tasks (where a silent failure would be unacceptable).

[alexitheodore]

Frustratingly I am having the same issue. Turns out my issue was that I wasn't supplying a password and was expecting that because I was executing as a user that had "trust" (and also .pgass) that it wouldn't need a password - or even more assumingly, that it would say that "password invalid". But lo, behold... you must copy/paste the password in plain text for everyone to see and keep track of.

[woodchuck]

@alexitheodore Thank you! This was my issue. I expected to be prompted for the password. if you export DB_PASS='password', then you can avoid supplying it with the command. The initial space will hide it from your terminal history.

[inspector71]

This is a common issue with PGFutter and one that we all run into, at some point, there's a PR open since 2019 to improve the handling of errors: https://github.com/lukasmartinelli/pgfutter/pull/67/files but it doesn't look like this situation will change anytime soon.

My recommendation would be to try trial and error, check your postgress logging and look for alternatives for production tasks (where a silent failure would be unacceptable).

I guess this is a stalled project then. Hopefully @lukasmartinelli is OK and might be able to fire things up again.

Otherwise would be great if someone could fork it and get it going. Unfortunately I don't have the Python experience.