Re: Separate psql commands from arguments

From: Gregory Stark <stark(at)enterprisedb(dot)com>
To: "Bernd Helmle" <mailings(at)oopsware(dot)de>
Cc: "Decibel!" <decibel(at)decibel(dot)org>, "Peter Eisentraut" <peter_e(at)gmx(dot)net>, <pgsql-hackers(at)postgresql(dot)org>, "Brendan Jurd" <direvus(at)gmail(dot)com>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: Separate psql commands from arguments
Date: 2008-04-11 09:57:20
Message-ID: 87lk3khfy7.fsf@oxford.xeocode.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


"Bernd Helmle" <mailings(at)oopsware(dot)de> writes:

>> What happens to aliases when you change the encoding in the middle of
>> running one? Actually, come to think of it, what *does* happen to aliases
>> when the encoding changes??
>
> Hmm? What happens if you are going to change your encoding within multiple
> backslash commands now?

I mean. What happens if I do:

\encoding 'UTF8'
\alias foo select 'あ' from tab;
\encoding euc-jp
\foo

What encoding is the alias itself stored in? Do we have to worry about
converting it when you switch client-encodings?

--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's RemoteDBA services!

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Hannu Krosing 2008-04-11 10:00:04 Re: Adding pipelining support to set returning functions
Previous Message Martijn van Oosterhout 2008-04-11 09:48:46 Re: question on how to correctly communicate with external library functions which return malloc()'ed strings