So you are asking about compiling with multibyte and then using ASCII
for some initdb's and Unicode for others. There are certain routines
that get replaced for multibyte/unicode which are slower than the
ASCII-only alternatvies, and these do apply to all databases, whether
initdb'ed with multibyte or not. There is some penalty, and that is why
we don't enable multibyte by default.
---------------------------------------------------------------------------
Arsalan Zaidi wrote:
> > I read somewhere in the docs that turning on multi-byte support slows PG
> > down.
> >
> > I was wondering. If I compile multi-byte support in and then use PG to
> > access
> > both a db initdb'ed with supprot for UNICODE and another one which uses
> > plain
> > ASCII, will there be a difference in speed between the two?
> >
> > Will PG run as normal with the ASCII db and slower with the UNICODE db or
> > slower with both?
> >
> > Thanks in advance.
> >
> > --Arsalan.
> >
> > -------------------------------------------------------------------
> > People often hate those things which they do not know, or cannot
> understand.
> > --Ali Ibn Abi Talib (A.S.)
> >
> >
> > ---------------------------(end of broadcast)---------------------------
> > TIP 5: Have you checked our extensive FAQ?
> >
> > http://www.postgresql.org/users-lounge/docs/faq.html
> >
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo@postgresql.org so that your
> message can get through to the mailing list cleanly
>
--
Bruce Momjian | http://candle.pha.pa.us
pgman@candle.pha.pa.us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026