Обсуждение: PostgreSQL and ZFS

Поиск
Список
Период
Сортировка

PostgreSQL and ZFS

От
Thomas Bräutigam
Дата:
Hello,
 
I am working with a PostgreSQL Database and I want to change the Filesystem to ZFS.
 
Does someone have experience with PostgreSQL and its Performance with ZFS? Are the current write options for PostgreSQL suitable for ZFS?
 
Do I need to finetune Postgres with the settings for ZFS?
Like finetuning of...
- fsync
- wal_sync_method
 
Thanks if someone can help me on this.
 
Cheers Thomas

Database encoding

От
"Anibal David Acosta"
Дата:

Hello, I have a postgresql installed with encoding “WIN1252”.

 

But I need to create a DB with LATIN1 encoding, when I try I got the error: “Encoding Latin1 does not match server’s locale Spanish_Spain.1252. The servers’s LC_CTYPE setting require encoding WIN1252

 

 

Is possible to change the server encoding to LATIN1?

 

 

Thanks for your help!

 

 

Re: Database encoding

От
"Jeremy Tunnell"
Дата:
The setting is in a file called i18n, but I can't recall where it's located.

On Wed, Sep 3, 2008 at 6:40 AM, Anibal David Acosta <aa@personal.net.py> wrote:

Hello, I have a postgresql installed with encoding "WIN1252".

 

But I need to create a DB with LATIN1 encoding, when I try I got the error: "Encoding Latin1 does not match server's locale Spanish_Spain.1252. The servers's LC_CTYPE setting require encoding WIN1252

 

 

Is possible to change the server encoding to LATIN1?

 

 

Thanks for your help!

 

 


Re: Database encoding

От
valgog
Дата:
On Sep 3, 3:40 pm, a...@personal.net.py ("Anibal David Acosta") wrote:
> Hello, I have a postgresql installed with encoding "WIN1252".
>
> But I need to create a DB with LATIN1 encoding, when I try I got the error:
> "Encoding Latin1 does not match server's locale Spanish_Spain.1252. The
> servers's LC_CTYPE setting require encoding WIN1252
>
> Is possible to change the server encoding to LATIN1?
>
> Thanks for your help!

You should use the same encoding for your DB instance as you used when
creating a DB with initdb. Usually it makes sense to always use UTF8
as your encoding... in case you will need some non-LATIN1
characters... you can check which encoding was used when creating a DB
with show lc_ctype...

Regards,

-- Valentine

P.S.: there are many posts related to that issue. You can look up a
BUG mailing list for collate and encoding.