Re: Problem running native windows Postgres 8 pg_dump etc on
Magnus wrote:
You should run the Cygwin tools from Cygwin. They work fine against a
native backend.
Thanks, I'll have to wait for the port of P8.0.0 rc4 to cygwin as the
current cygwin port of pg_dump is 8.0.0 B2 and does not work correctly for
reason of the error 'column "nsptablespace" does not exist' which is fixed
in later pg_dump versions.
Still intrigued as to why the native ports don't work though.
Regards
Laurie
:.________________
CONFIDENTIALITY : This e-mail and any attachments are confidential and
may be privileged. If you are not a named recipient, please notify the
sender immediately and do not disclose the contents to another person, use
it for any purpose or store or copy the information in any medium.
You should run the Cygwin tools from Cygwin. They work fine
against a
native backend.
Thanks, I'll have to wait for the port of P8.0.0 rc4 to
cygwin as the current cygwin port of pg_dump is 8.0.0 B2 and
does not work correctly for reason of the error 'column
"nsptablespace" does not exist' which is fixed in later
pg_dump versions.Still intrigued as to why the native ports don't work though.
Cygwin has a different handling of console input/output than the windows
command prompt. I've seen similar weird errors with other native windows
tools on the cygwin shell.
//Magnus
Import Notes
Resolved by subject fallback