В Пнд, 07.07.2003, в 10:12, Soeren Laursen пишет:
> It looked like that worked,
>
> How about large objects (blobs). That is the reason I use custom
> format or am I missing a point here?
>
> I guess I might could use a lot of switches and only dump the
> blobs in a single file?
I'm sorry, som
It looked like that worked,
How about large objects (blobs). That is the reason I use custom
format or am I missing a point here?
I guess I might could use a lot of switches and only dump the
blobs in a single file?
Regards,
Søren,
> Ð Ðнд, 07.07.2003, в 00:01, Soeren Laursen пиÑеÑ:
>
В Пнд, 07.07.2003, в 00:01, Soeren Laursen пишет:
> Hi,
>
> I am not sure how and where I should use the \encoding latin1
>
> Something like,
>
> psql test01
> \encodinng latin1
> \q
>
> pg_restore .
Ah. Load the backup in a non-unicode database, dump it using the text
format (i.e. not th
Hi,
I am not sure how and where I should use the \encoding latin1
Something like,
psql test01
\encodinng latin1
\q
pg_restore .
Regards
Søren,
> Ð ÐÑк, 06.07.2003, в 19:57, Soeren Laursen пиÑеÑ:
>
> > pg_restore: ERROR: copy: line 1, Invalid UNICODE character sequence
> > foun
В Вск, 06.07.2003, в 19:57, Soeren Laursen пишет:
> pg_restore: ERROR: copy: line 1, Invalid UNICODE character sequence
> found (0xf87665)
> No need to say that the new database is created with UNICODE
> encoding?!
use
\encoding latin1
once when you import the data. That'll convert the data f
Hi All,
I am upgrading my server 7.1 (a debian potato) to a new server 7.2 (a
debian woody).
On the 7.1 server I had a script that took a backup of my databases
each day using pg_dump:
/usr/local/pgsql/bin/vacuumdb -z -h localhost -U postgres $i
>/dev/null 2>&1
/usr/local/pgsql/bin/pg_dump -b -F
