Le 23/12/2010 15:14, Mark Watson a écrit :
> Hello group,
> Any suggestions as to how to fix this are greatly appreciated.
> My setup is Vista, locally installed Postgres 8.4.6 in default folders with
> db initialised as (server_encoding) UTF8, and databases created with default
> encoding of WIN12
Hello again,
Problem below solved if in fact PgAdmin only displays UTF8.
Hello group,
Any suggestions as to how to fix this are greatly appreciated.
My setup is Vista, locally installed Postgres 8.4.6 in default folders with
db initi
Hello group,
Any suggestions as to how to fix this are greatly appreciated.
My setup is Vista, locally installed Postgres 8.4.6 in default folders with
db initialised as (server_encoding) UTF8, and databases created with default
encoding of WIN1252. My application program is behaving correctly usin
On Sun, Aug 3, 2008 at 9:38 PM, Tom Lane <[EMAIL PROTECTED]> wrote:
> "Andrew Goodnough" <[EMAIL PROTECTED]> writes:
> > I'm using these commands to perform a dump and load.
> > pg_dump -c lakevie_typo | gzip > $HOME/backups/typo_$DATE.sql.gz
> > gzip < $HOME/backups/typo_$DATE.sql.gz |psql -d lak
To: pgsql-admin@postgresql.org
Sent: Monday, August 04, 2008 7:29 AM
Subject: [ADMIN] client_encoding error on load
I'm using these commands to perform a dump and load.
pg_dump -c lakevie_typo | gzip > $HOME/backups/typo_$DATE.sql.gz
gzip < $HOME/backups/typo_$DATE.sql.g
"Andrew Goodnough" <[EMAIL PROTECTED]> writes:
> I'm using these commands to perform a dump and load.
> pg_dump -c lakevie_typo | gzip > $HOME/backups/typo_$DATE.sql.gz
> gzip < $HOME/backups/typo_$DATE.sql.gz |psql -d lakevie_typobak -f -
Surely the second step must start with gunzip?
I'm using these commands to perform a dump and load.
pg_dump -c lakevie_typo | gzip > $HOME/backups/typo_$DATE.sql.gz
gzip < $HOME/backups/typo_$DATE.sql.gz |psql -d lakevie_typobak -f -
The dump is fine but the load only works if I first extract the sql, then
run it. Running it using the pipe t
