[Rt-devel] PostgreSQL 8.4.4 and rt3 encoding

Thu Jul 29 13:50:28 EDT 2010

Peter -
Not sure why the DBAs want LATIN1 or SQL_ASCII. They state "none of the
other databases are UTF8'.

The DBAs just allowed me to be a preliminary tester. So, on our test
server, I  created the RT db with the default encoding, LATIN1. Then
manually set the encoding to UTF8.

   #create database rt3 encoding = 'UTF8';
   ERROR:  encoding UTF8 does not match locale en_US
   DETAIL:  The chosen LC_CTYPE setting requires encoding LATIN1.
   #create database rt3 encoding = 'LATIN1';
   ... created database from dump....

     rt3=# SET client_encoding = 'UTF8';
     SET
     rt3=# SHOW client_encoding;
     client_encoding
     -----------------
      UTF8

I created a few tickets in on our development webserver using the new DB.
Nothing hinkey so far.

Thanks for following up....

Sharon

  From:       "Peter C. Lai" <peter at simons-rock.edu>                                                     

  To:         Sharon.Belliveau at frb.gov                                                                   

  Cc:         rt-devel at lists.bestpractical.com                                                           

  Date:       07/29/2010 01:43 PM                                                                        

  Subject:    Re: [Rt-devel] PostgreSQL 8.4.4  and rt3 encoding                                          

Is there a reason why your DBA does not set the default encoding to UTF8?
It has been the standard default encoding throughout the entire 8.x
postgresql
series.

Is there a reason why you cannot create the RT db with UTF8 before doing
the
restore?

On 2010-07-29 09:54:15AM -0400, Sharon.Belliveau at frb.gov wrote:
> Per the DBA:
> The database cluster will be initialized with locale en_US.
> The default database encoding has accordingly been set to LATIN1.
> The default text search configuration will be set to "english".
>
> We RT admins would like to keep the encoding that will work best with RT
> and not be constrained for future RT upgrades.  So, will we incur
problems
> if we give in to setting the encoding to LATIN1 or SQL_ASCII?
>
> -Sharon
>
>
>
>

>   From:       "Peter C. Lai" <peter at simons-rock.edu>

>

>   To:         Sharon.Belliveau at frb.gov

>

>   Cc:         rt-devel at lists.bestpractical.com

>

>   Date:       07/28/2010 05:05 PM

>

>   Subject:    Re: [Rt-devel] PostgreSQL 8.4.4  and rt3 encoding

>

>
>
>
>
>
> Why would you want this?!
>
> On 2010-07-28 04:13:48PM -0400, Sharon.Belliveau at frb.gov wrote:
> >
> > Hello -
> > We are working with RT 3.8. Our DBAs are upgrading our PostgreSQL
> > installation to 8.4.4.  I was asked if the rt3 database, currently
> encoded
> > as UTF8 could be changed to either latin1 or sql_ascii. I've been
> searching
> > the list archives and RT's docs and can't seem to find a database
> encoding
> > recommendation.  So,would anyone offer advice on which encoding method
to
> > use or avoid? Any experience with PostgreSQL 8.4.4 to share?
> >
> > Sharon
> >
> > _______________________________________________
> > List info:
> http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-devel
>
> --
> ===========================================================
> Peter C. Lai                 | Bard College at Simon's Rock
> Systems Administrator        | 84 Alford Rd.
> Information Technology Svcs. | Gt. Barrington, MA 01230 USA
> peter AT simons-rock.edu     | (413) 528-7428
> ===========================================================
>
>
>
>

--
===========================================================
Peter C. Lai                 | Bard College at Simon's Rock
Systems Administrator        | 84 Alford Rd.
Information Technology Svcs. | Gt. Barrington, MA 01230 USA
peter AT simons-rock.edu     | (413) 528-7428
===========================================================