Skip site navigation (1) Skip section navigation (2)

Re: Show encoding in initdb messages

From: "Magnus Hagander" <mha(at)sollentuna(dot)net>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>,"Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au>
Cc: "Patches" <pgsql-patches(at)postgresql(dot)org>
Subject: Re: Show encoding in initdb messages
Date: 2004-06-21 14:55:54
Message-ID: 6BCB9D8A16AC4241919521715F4D8BCE34BD0B@algol.sollentuna.se (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-patches
> > The reason it will help with support is because newbies will go 
> > "SQL_ASCII! I don't want ascii!".
> 
> No they won't.  They will likely not even notice this message 
> in the sea of other messages they've never seen before; and 
> even if they do notice it, they will certainly not realize 
> that they don't want it.  If the message were to *say* "this 
> is probably a bad choice because it's incompatible with your 
> locale selection", then it might possibly have the effect 
> you're hoping for, but I don't see how we can find that out.

Another way would be to make -E a mandatory parameter, and remove the
default completely. That way you have to make a conscious decision.
Can't claim surprise then.


//Magnus

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2004-06-21 15:12:11
Subject: Re: Show encoding in initdb messages
Previous:From: Merlin MoncureDate: 2004-06-21 14:39:41
Subject: Re: Compile failure with SSL

pgsql-patches by date

Next:From: Tom LaneDate: 2004-06-21 15:12:11
Subject: Re: Show encoding in initdb messages
Previous:From: Tom LaneDate: 2004-06-21 14:44:29
Subject: Re: Show encoding in initdb messages

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group