Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1Y18jU-0006Do-5k for pgsql-novice@arkaria.postgresql.org; Wed, 17 Dec 2014 07:09:16 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1Y18jT-0000rB-IJ for pgsql-novice@arkaria.postgresql.org; Wed, 17 Dec 2014 07:09:15 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1Y18jR-0000oV-H4 for pgsql-novice@postgresql.org; Wed, 17 Dec 2014 07:09:13 +0000 Received: from mail-pd0-x229.google.com ([2607:f8b0:400e:c02::229]) by magus.postgresql.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:256) (Exim 4.80) (envelope-from ) id 1Y18jJ-0001kq-2L for pgsql-novice@postgresql.org; Wed, 17 Dec 2014 07:09:12 +0000 Received: by mail-pd0-f169.google.com with SMTP id z10so15694773pdj.0 for ; Tue, 16 Dec 2014 23:09:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type; bh=H2c3I5Oj7oigzAPAMRR3THKMzaObqM22hAK+lLOZqVM=; b=mawcFkSkZq3yFGj4FVibo9HsjFJsKp5JwQWZODV2oLP2fhOkl6HSz5av78xj1so6Z0 wOijWKE0E8tPrT+bptuE1YHMSHwuGY8xswny5gCs+r1HWmRpSF6GTKutpG6YLvOKfK/9 HqQVO5B3TH4gwUgoyl4vmeUIsnwsOV1q7nQ6x6KevH5v8kHIxUXQWnmVdO79dNJxLHKd 68RNZqS2WvbZyheJFPBKPQh4IxCY/D/Z2By4GOBom5OjpfmJVje2IaayVuotFr7ETdHP 27Oa7ttFrT5v/JPDgsybegg9gSzz/dUmv27jCpdyN4MAzL/SQkFq0oYkuRARFZ5oAcGd zOhg== X-Received: by 10.69.8.99 with SMTP id dj3mr2305142pbd.16.1418800142370; Tue, 16 Dec 2014 23:09:02 -0800 (PST) Received: from [127.0.0.1] ([121.54.58.132]) by mx.google.com with ESMTPSA id fn4sm2921288pab.39.2014.12.16.23.08.58 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 16 Dec 2014 23:09:01 -0800 (PST) Message-ID: <54912BFC.4020408@gmail.com> Date: Wed, 17 Dec 2014 15:08:44 +0800 From: Scott Robertson User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:15.0) Gecko/20120907 Thunderbird/15.0.1 MIME-Version: 1.0 To: pgsql-novice@postgresql.org Subject: Re: warning about console code page on starting psql References: <54910242.3090706@gmail.com> <549113EA.2010007@gmail.com> <1418795707357-5831042.post@n5.nabble.com> In-Reply-To: Content-Type: multipart/alternative; boundary="------------000302020108060307050503" X-Antivirus: avast! (VPS 141216-2, 12/17/2014), Outbound message X-Antivirus-Status: Clean X-Pg-Spam-Score: -1.9 (-) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-novice Precedence: bulk Sender: pgsql-novice-owner@postgresql.org This is a multi-part message in MIME format. --------------000302020108060307050503 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit On 12/17/2014 2:15 PM, David Johnston wrote: > Please send all replies to the list and either inline or bottom post. > > On Tuesday, December 16, 2014, Scott Robertson > > wrote: > > Thanks David, I am starting to understand the console is what they > used > to call a dos prompt, the little black window where psql appears. > > > Correct. > > > > As you say, the font change had no effect on the Windows command > prompt > console that I open from the Windows start menu. However, the font > change did persist in psql. Each time I reopen psql, it is now > automatically in Lucida Console font. > > > Must be some memorized state being saved by Windows and the means by > which you are launching psql. > > > > It seems I should be able to get to C:\> from the same (psql) console, > but don't know how, or how to get back to psql if I did. And don't > know > if there's any reason to. > > It sounds like you're saying that I should type this command in > the psql > console each time I open it. In which case, I'd have to get to the > C:\> > in order to do it, since it's not a psql command. > > > I don't know psql is launched on windows (or, specifically, how you > are launching it) so cannot answer that particular question. Using > "start->run" you can type "cmd" then in the resulting console change > the codepage before manually running "psql" Tried this, nothing changed. > > Shortcut properties can be explored if indeed that is what is being > used to launch psql. Yes, I had a shortcut for psql in the program files start menu of Windows, which I moved to the desktop. I don't know another way to open it. Shortcut target is "C:\Program Files\PostgreSQL\9.4\scripts\runpsql.bat" Start in location is "C:\Program Files\PostgreSQL\9.4\scripts" > > If your are in psql already what happens when you type "\q" ? psql says "type any key to continue" and if you do, psql quits. > > > However, returning to my original post, I have already determined that > Windows is set to 1252 as (?) instructed by pg documentation, and is > still giving the same error. Is there a windows configuration file I > should edit or...??? > > > You don't change the Windows codepage - you change the console to > match whatever Windows is using. > > David J. > --- This email has been checked for viruses by Avast antivirus software. http://www.avast.com --------------000302020108060307050503 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit
On 12/17/2014 2:15 PM, David Johnston wrote:
Please send all replies to the list and either inline or bottom post.

On Tuesday, December 16, 2014, Scott Robertson <stumpednomore@gmail.com> wrote:
Thanks David, I am starting to understand the console is what they used
to call a dos prompt, the little black window where psql appears.

Correct.
 

As you say, the font change had no effect on the Windows command prompt
console that I open from the Windows start menu. However, the font
change did persist in psql. Each time I reopen psql, it is now
automatically in Lucida Console font.

Must be some memorized state being saved by Windows and the means by which you are launching psql.
 

It seems I should be able to get to C:\> from the same (psql) console,
but don't know how, or how to get back to psql if I did. And don't know
if there's any reason to.

It sounds like you're saying that I should type this command in the psql
console each time I open it. In which case, I'd have to get to the C:\>
in order to do it, since it's not a psql command.

I don't know psql is launched on windows (or, specifically, how you are launching it) so cannot answer that particular question.  Using "start->run" you can type "cmd" then in the resulting console change the codepage before manually running "psql"
Tried this, nothing changed.

Shortcut properties can be explored if indeed that is what is being used to launch psql.
Yes, I had a shortcut for psql in the program files start menu of Windows, which I moved to the desktop. I don't know another way to open it.

Shortcut target is "C:\Program Files\PostgreSQL\9.4\scripts\runpsql.bat"
Start in location is "C:\Program Files\PostgreSQL\9.4\scripts"

If your are in psql already what happens when you type "\q" ?
psql says "type any key to continue" and if you do, psql quits.


However, returning to my original post, I have already determined that
Windows is set to 1252 as (?) instructed by pg documentation, and is
still giving the same error. Is there a windows configuration file I
should edit or...???

You don't change the Windows codepage - you change the console to match whatever Windows is using. 

David J.



This email has been checked for viruses by Avast antivirus software.
www.avast.com


--------------000302020108060307050503--