On Mon, Oct 26, 2009 at 9:03 AM, Tom Lane wrote:
>
> I suspect the largest practical risk is that different OSes might assign
> different behaviors to the same locale name. There's really no good way
> for Postgres to detect that :-(
>
Alvaro just remembers me that tablespaces path could be a pr
2009/11/26 Melanie Hofmann :
> Hello,
>
> I'm a very big problem. I want to load shapefiles in a postgresql with
> shp2pgsql and psql. So i create the statement on a windows DOS console. I
> get below error FEHLER: ungültige Byte-Sequenz für Kodierung UTF8 0xd627.
>
> My Client_encoding is
>
> tem
Hello,
I'm a very big problem. I want to load shapefiles in a postgresql with
shp2pgsql and psql. So i create the statement on a windows DOS console. I
get below error FEHLER: ungültige Byte-Sequenz für Kodierung UTF8 0xd627.
My Client_encoding is
template_postgis=# SHOW CLIENT_ENCODING;
clien
"Joshua D. Drake" writes:
> http://pgfoundry.org/projects/skytools/
See also: http://wiki.postgresql.org/wiki/Londiste_Tutorial
Regards,
--
dim
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admi