And many others errors when xsome user connect to database x, schema
xxx. PG 8.4.
Problems started about same time as search_path has SET.
search_path has reset, but did'nt help.
ALTER DATABASE x SET search_path=some, public;
-- xxx wasn't in that list
ALTER DATABASE x RESET search_path; - has
And many others errors when xsome user connect to database x, schema
xxx. PG 8.4.
Problems started about same time as search_path has SET.
search_path has reset, but did'nt help.
ALTER DATABASE x SET search_path=some, public;
-- xxx wasn't in that list
ALTER DATABASE x RESET search_path; - has
I have installed cycwin and sshd in my Windows server.
I have Winnative psql.exe (8.3.5)
If I use cygwin locally in this server and give command in cygwin session:
psql -h somehost -U someuser -d somedb
it works fine
But if i use via ssh same way, then no echo ... and process hang.
I have
Jukka Inkeri wrote:
I have installed cycwin and sshd in my Windows server.
I have Winnative psql.exe (8.3.5)
If I use cygwin locally in this server and give command in cygwin session:
psql -h somehost -U someuser -d somedb
it works fine
But if i use via ssh same way, then no echo ... and
The native psql is written for Windows, not for Cygwin. You really
shouldn't be using it there... If you are using Cygwin, you should be
using a Cygwin psql.exe.
PG pages says: use native, not cygwin version anymore. It's not problem
if it's "windows" binary, you can use many native binary
> have a shell script that
performs a full online backup of postgres?
Full backup ex. pg_dumpall
Daily backup (dump) / database:
- - - - - - - - - - - - - - -
#!/someshellpath like /bin/sh or /bin/bash or /bin/ksh ...
#daily.sh
#default plaintext
#usage: daily.sh [c|t|p]
#
PORT=5432
HOST="loca
