| From: | Peter Eisentraut <e99re41(at)DoCS(dot)UU(dot)SE> |
|---|---|
| To: | SAKAIDA <sakaida(at)psn(dot)co(dot)jp> |
| Cc: | Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp>, pgsql-hackers(at)postgreSQL(dot)org |
| Subject: | Re: [HACKERS] libpq+MB/putenv(), getenv() clean up |
| Date: | 2000-01-13 11:23:49 |
| Message-ID: | Pine.GSO.4.02A.10001131222280.6438-100000@Pingvin.DoCS.UU.SE |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, 13 Jan 2000, SAKAIDA wrote:
> Do those changes mean that libpq(or psql) always has the MULTIBYTE
> function?
>
> Now, libpq's MULTIBYTE function is a compile option(--with-mb).
> But, I always want the MULTIBYTE function, even if PostgreSQL have
> *not* been made with "--with-mb" option. Because, I want to access
> two kind of PostgreSQL servers(named A and B) by using the B's psql.
> (Here, A server is "--with-mb" and B server is not "--with-mb".)
Aah, that's a good point, but an always-on psql and libpq is much slower.
But you could use the psql that stems from the multibyte compile, or not?
--
Peter Eisentraut Sernanders vaeg 10:115
peter_e(at)gmx(dot)net 75262 Uppsala
http://yi.org/peter-e/ Sweden
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Meskes | 2000-01-13 11:26:18 | Another item for TODO list |
| Previous Message | Peter Eisentraut | 2000-01-13 11:21:27 | Re: [HACKERS] TODO list updated |