psql output in Debian is messed up

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
2
down vote

favorite












Width of the terminal window is 280 columns, and Debian prints text just fine.



However, psql output is totally messed up. When I type a command, it's not wrapped: if I exceed 80 symbols in a line, the rest is printed from the beginning of the line overlapping the first part (i. e. caret is returned).enter image description here Same goes for printing query results: it tries to fits everything into 80 symbols per line, but at least doesn't overlap the text.



I've tried this command: pset columns 280, but it didn't help.



echo "$PS1" yields $debian_chroot:+($debian_chroot)u@h:w$






debian terminal







share|improve this question























  • A strong suspect here is your prompt string contains non-printing characters that confuse the shell's understanding of the current cursor; can you provide the output of echo "$PS1"?
    – Jeff Schaller
    4 hours ago










  • @JeffSchaller Added this info. Also, I've messed up a bit: it's not Ubuntu, it's Debian.
    – efpies
    4 hours ago














up vote
2
down vote

favorite












Width of the terminal window is 280 columns, and Debian prints text just fine.



However, psql output is totally messed up. When I type a command, it's not wrapped: if I exceed 80 symbols in a line, the rest is printed from the beginning of the line overlapping the first part (i. e. caret is returned).enter image description here Same goes for printing query results: it tries to fits everything into 80 symbols per line, but at least doesn't overlap the text.



I've tried this command: pset columns 280, but it didn't help.



echo "$PS1" yields $debian_chroot:+($debian_chroot)u@h:w$






debian terminal







share|improve this question























  • A strong suspect here is your prompt string contains non-printing characters that confuse the shell's understanding of the current cursor; can you provide the output of echo "$PS1"?
    – Jeff Schaller
    4 hours ago










  • @JeffSchaller Added this info. Also, I've messed up a bit: it's not Ubuntu, it's Debian.
    – efpies
    4 hours ago












up vote
2
down vote

favorite









up vote
2
down vote

favorite











Width of the terminal window is 280 columns, and Debian prints text just fine.



However, psql output is totally messed up. When I type a command, it's not wrapped: if I exceed 80 symbols in a line, the rest is printed from the beginning of the line overlapping the first part (i. e. caret is returned).enter image description here Same goes for printing query results: it tries to fits everything into 80 symbols per line, but at least doesn't overlap the text.



I've tried this command: pset columns 280, but it didn't help.



echo "$PS1" yields $debian_chroot:+($debian_chroot)u@h:w$






debian terminal







share|improve this question















Width of the terminal window is 280 columns, and Debian prints text just fine.



However, psql output is totally messed up. When I type a command, it's not wrapped: if I exceed 80 symbols in a line, the rest is printed from the beginning of the line overlapping the first part (i. e. caret is returned).enter image description here Same goes for printing query results: it tries to fits everything into 80 symbols per line, but at least doesn't overlap the text.



I've tried this command: pset columns 280, but it didn't help.



echo "$PS1" yields $debian_chroot:+($debian_chroot)u@h:w$






debian terminal




debian terminal






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited 4 hours ago

























asked 4 hours ago









efpies

1185




1185











  • A strong suspect here is your prompt string contains non-printing characters that confuse the shell's understanding of the current cursor; can you provide the output of echo "$PS1"?
    – Jeff Schaller
    4 hours ago










  • @JeffSchaller Added this info. Also, I've messed up a bit: it's not Ubuntu, it's Debian.
    – efpies
    4 hours ago
















  • A strong suspect here is your prompt string contains non-printing characters that confuse the shell's understanding of the current cursor; can you provide the output of echo "$PS1"?
    – Jeff Schaller
    4 hours ago










  • @JeffSchaller Added this info. Also, I've messed up a bit: it's not Ubuntu, it's Debian.
    – efpies
    4 hours ago















A strong suspect here is your prompt string contains non-printing characters that confuse the shell's understanding of the current cursor; can you provide the output of echo "$PS1"?
– Jeff Schaller
4 hours ago




A strong suspect here is your prompt string contains non-printing characters that confuse the shell's understanding of the current cursor; can you provide the output of echo "$PS1"?
– Jeff Schaller
4 hours ago












@JeffSchaller Added this info. Also, I've messed up a bit: it's not Ubuntu, it's Debian.
– efpies
4 hours ago




@JeffSchaller Added this info. Also, I've messed up a bit: it's not Ubuntu, it's Debian.
– efpies
4 hours ago










1 Answer
1






active

oldest

votes

















up vote
3
down vote



accepted










The solution is to completely reset a PSQL installation, so it is in the same state as when It was installed. Debian splits the database configuration from the database files, opposed to generic PSQL installation that puts everything under same directory. Debian allows multiple clusters and even different versions of PSQL to coexist in same host.



Configuration files: /etc/postgresql/[version]/[cluster]/
Binaries: /usr/lib/postgresql/[version]
Data files: /var/lib/postgresql/[version]/[cluster]


Debian PSQL installation automatically calls the initdb i.e. it initializes the cluster with default encoding and locale. Encoding can be changed later but the locale cannot. To change the locale (possibly other options in initdb), delete the existing default cluster and create a new one:



-Take root privileges.



-Run the following command:



pg_dropcluster --stop <version> main

For example:
pg_dropcluster --stop 8.3 main


-Run the initdb with your options. For example:



pg_createcluster --locale de_DE.UTF-8 --start 8.3 main





share|improve this answer


















  • 1




    Thanks. That helped. I've only had C.UTF-8 locale (it's a VM, not a machine for work), but it was enough.
    – efpies
    3 hours ago










Your Answer







StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
convertImagesToLinks: false,
noModals: false,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);













 

draft saved


draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f470935%2fpsql-output-in-debian-is-messed-up%23new-answer', 'question_page');

);

Post as a guest

















1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes








up vote
3
down vote



accepted










The solution is to completely reset a PSQL installation, so it is in the same state as when It was installed. Debian splits the database configuration from the database files, opposed to generic PSQL installation that puts everything under same directory. Debian allows multiple clusters and even different versions of PSQL to coexist in same host.



Configuration files: /etc/postgresql/[version]/[cluster]/
Binaries: /usr/lib/postgresql/[version]
Data files: /var/lib/postgresql/[version]/[cluster]


Debian PSQL installation automatically calls the initdb i.e. it initializes the cluster with default encoding and locale. Encoding can be changed later but the locale cannot. To change the locale (possibly other options in initdb), delete the existing default cluster and create a new one:



-Take root privileges.



-Run the following command:



pg_dropcluster --stop <version> main

For example:
pg_dropcluster --stop 8.3 main


-Run the initdb with your options. For example:



pg_createcluster --locale de_DE.UTF-8 --start 8.3 main





share|improve this answer


















  • 1




    Thanks. That helped. I've only had C.UTF-8 locale (it's a VM, not a machine for work), but it was enough.
    – efpies
    3 hours ago














up vote
3
down vote



accepted










The solution is to completely reset a PSQL installation, so it is in the same state as when It was installed. Debian splits the database configuration from the database files, opposed to generic PSQL installation that puts everything under same directory. Debian allows multiple clusters and even different versions of PSQL to coexist in same host.



Configuration files: /etc/postgresql/[version]/[cluster]/
Binaries: /usr/lib/postgresql/[version]
Data files: /var/lib/postgresql/[version]/[cluster]


Debian PSQL installation automatically calls the initdb i.e. it initializes the cluster with default encoding and locale. Encoding can be changed later but the locale cannot. To change the locale (possibly other options in initdb), delete the existing default cluster and create a new one:



-Take root privileges.



-Run the following command:



pg_dropcluster --stop <version> main

For example:
pg_dropcluster --stop 8.3 main


-Run the initdb with your options. For example:



pg_createcluster --locale de_DE.UTF-8 --start 8.3 main





share|improve this answer


















  • 1




    Thanks. That helped. I've only had C.UTF-8 locale (it's a VM, not a machine for work), but it was enough.
    – efpies
    3 hours ago












up vote
3
down vote



accepted







up vote
3
down vote



accepted






The solution is to completely reset a PSQL installation, so it is in the same state as when It was installed. Debian splits the database configuration from the database files, opposed to generic PSQL installation that puts everything under same directory. Debian allows multiple clusters and even different versions of PSQL to coexist in same host.



Configuration files: /etc/postgresql/[version]/[cluster]/
Binaries: /usr/lib/postgresql/[version]
Data files: /var/lib/postgresql/[version]/[cluster]


Debian PSQL installation automatically calls the initdb i.e. it initializes the cluster with default encoding and locale. Encoding can be changed later but the locale cannot. To change the locale (possibly other options in initdb), delete the existing default cluster and create a new one:



-Take root privileges.



-Run the following command:



pg_dropcluster --stop <version> main

For example:
pg_dropcluster --stop 8.3 main


-Run the initdb with your options. For example:



pg_createcluster --locale de_DE.UTF-8 --start 8.3 main





share|improve this answer














The solution is to completely reset a PSQL installation, so it is in the same state as when It was installed. Debian splits the database configuration from the database files, opposed to generic PSQL installation that puts everything under same directory. Debian allows multiple clusters and even different versions of PSQL to coexist in same host.



Configuration files: /etc/postgresql/[version]/[cluster]/
Binaries: /usr/lib/postgresql/[version]
Data files: /var/lib/postgresql/[version]/[cluster]


Debian PSQL installation automatically calls the initdb i.e. it initializes the cluster with default encoding and locale. Encoding can be changed later but the locale cannot. To change the locale (possibly other options in initdb), delete the existing default cluster and create a new one:



-Take root privileges.



-Run the following command:



pg_dropcluster --stop <version> main

For example:
pg_dropcluster --stop 8.3 main


-Run the initdb with your options. For example:



pg_createcluster --locale de_DE.UTF-8 --start 8.3 main






share|improve this answer














share|improve this answer



share|improve this answer








edited 3 hours ago

























answered 4 hours ago









Goro

4,07752254




4,07752254







  • 1




    Thanks. That helped. I've only had C.UTF-8 locale (it's a VM, not a machine for work), but it was enough.
    – efpies
    3 hours ago












  • 1




    Thanks. That helped. I've only had C.UTF-8 locale (it's a VM, not a machine for work), but it was enough.
    – efpies
    3 hours ago







1




1




Thanks. That helped. I've only had C.UTF-8 locale (it's a VM, not a machine for work), but it was enough.
– efpies
3 hours ago




Thanks. That helped. I've only had C.UTF-8 locale (it's a VM, not a machine for work), but it was enough.
– efpies
3 hours ago

















 

draft saved


draft discarded















































 


draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f470935%2fpsql-output-in-debian-is-messed-up%23new-answer', 'question_page');

);

Post as a guest
































































Comments

Post a Comment

Popular posts from this blog

What does second last employer means? [closed]

Image
Clash Royale CLAN TAG #URR8PPP .everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0; up vote -3 down vote favorite Say, for example I have worked in the following companies, Company A => 2010 - 2011 Company B => 2011 - 2012 Company C => 2012 - Till Date Company D => Have offer Now assume Company D is asking to submit documents from my second last employer. So from the list of companies given, which company would be qualified as second last employer? software-industry employer share | improve this question asked Aug 10 '14 at 5:16 Rajaprabhu Aravindasamy 559 1 6 13 closed as off-topic by Jim G., jmort253 ♦ Aug 11 '14 at 1:58 This question appears to be off-topic. The users who voted to close gave this specific reason: "Questions seeking advice on company-specific regulations, agreements, or policies should be directed to your manager or HR department. Questions that address...
Read more

Installing NextGIS Connect into QGIS 3?

Image
Clash Royale CLAN TAG #URR8PPP .everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0; up vote 1 down vote favorite Just acquired free version of NEXTGIS and trying to install the plugin for QGIS. It tells me it was not designed for version 3 of QGIS. How do I set up the QGIS-NEXTGIS interface then? qgis qgis-plugins nextgis share | improve this question edited 3 hours ago PolyGeo ♦ 51.9k 17 77 233 asked 4 hours ago IanGS 16 4 New contributor IanGS is a new contributor to this site. Take care in asking for clarification, commenting, and answering. Check out our Code of Conduct. add a comment  |  up vote 1 down vote favorite Just acquired free version of NEXTGIS and trying to install the plugin for QGIS. It tells me it was not designed for version 3 of QGIS. How do I set up the QGIS-NEXTGIS interface then? qgis qgis-plugin...
Read more

One-line joke

A one-liner is a joke that is delivered in a single line. A good one-liner is said to be pithy - concise and meaningful. [1] Comedians and actors use this comedic method as part of their act, e.g. Jimmy Carr, Tommy Cooper, Rodney Dangerfield, Norm Macdonald, Ken Dodd, Stewart Francis, Zach Galifianakis, Mitch Hedberg, Anthony Jeselnik, Milton Jones, Shappi Khorsandi, Jay London, Mark Linn-Baker, Demetri Martin, Groucho Marx, Dan Mintz, Emo Philips, Tim Vine, Steven Wright and Henny Youngman and Arnold Schwarzenegger. [ citation needed ] Many fictional characters are also known to deliver one-liners, including James Bond, who usually includes pithy and laconic quips after disposing of a villain. [ citation needed ] Examples "A baby seal walks into a club." "A dyslexic man walks into a bra." (Anonymous) "There are three types of people, those who can count and those who can't." "Venison's dear, isn't it?" (Jimmy Carr) "An escala...
Read more