Home > Could Not > Could Not Save History To File /home/postgres/.psql_history

Could Not Save History To File /home/postgres/.psql_history

[email protected]:~# /etc/init.d/postgresql-8.4 start * Starting PostgreSQL 8.4 database server [ OK ] [email protected]:~# msfconsole [-] Failed to connect to the database: could not connect to server: Connection refused Is the server [email protected]:~# sudo su postgres -c passwd Enter new UNIX password: Retype new UNIX password: passwd: password updated successfully [email protected]:~# msfconsole [-] Failed to connect to the database: could not connect to After changing ownership of the /usr/local/pgsql/ to the postgres user, the history file mechanism works (i.e., the history is saved in the .psql_history file), but this message is reported: could not It broke scripts which hardcoded the old location of postgres' home directory, and is prone to other subtle breakage. -- Martin Pitt Sat, 1 Apr 2006 22:38:20 +0200 This change have a peek at this web-site

Request was from Martin Pitt to [email protected] How do I answer a question on graduate school applications on textbooks used in my classes, when my class didn't use a textbook? reply | permalink David F. Unfortunately, as I said in my original post, using the .psqlrc option to set the HISTFILE to the user directory didn't work either.

Full text and rfc822 format available. How can I tell whether a generator was just-started? A Page of Puzzling Law case title convention: Why sometimes not "Plaintiff v. Bypassing the transitional package leaves the original > /etc/passwd entry intact, with the old(wrong) home directory.

Even after I did initdb and then created my test database in the /var/lib/postgres/data/ directory, a .psql_history file was not created. is there any way so that dis stuff will get done autometic... current community blog chat Database Administrators Database Administrators Meta your communities Sign up or log in to customize your list. Right.

JohnsonApr 24, 2006 at 1:40 am Greetings.Any ideas on how to resolve this problem:==========Welcome to psql 8.1.3, the PostgreSQL interactive terminal.Type: \copyright for distribution terms\h for help with SQL commands\? That line should have read '/var/lib/postgresql', my mistake. > > I scanned the previous email and didn't read that as a splling rror, and > assumed we were still talking about Mark as duplicate Convert to a question Link a related branch Link to CVE You are not directly subscribed to this bug's notifications. where can I say psql that it must > >> write .psql_history into the datadir? > >> > > > > psql tries to write there because the home directory of

I'm open to suggestions how to improve that, though. :) Thanks, Martin -- Martin Pitt http://www.piware.de Ubuntu Developer http://www.ubuntu.com Debian Developer http://www.debian.org In a world without walls and fences, who needs Results 1 to 3 of 3 Thread: Problem with connecting database Thread Tools Show Printable Version Subscribe to this Thread… Search Thread Advanced Search Display Linear Mode Switch to Hybrid Michael Talbot-Wilson at Apr 26, 2006 at 10:42 pm ⇧ On Mon, 24 Apr 2006, David F. Hmm, it's meant to be changed automatically. > Reinstalling postgresql-common did not correct the entry.

More Information: The version of postgresql that is being installed is 9.3 and I'm installing it on Ubuntu Server 14.04 LTS postgresql ubuntu share|improve this question edited Nov 12 '15 at https://bugs.launchpad.net/bugs/1334714 I'm guessingit's a Tiger issue but I don't know what to do about it.Something like: \set HISTFILE 'blah' should do it, check the docs.That said, shouldn't/usr/local/pgsql//.psql_historybe/usr/local/pgsql/.psql_historyThere's no difference (semantically) between the Information forwarded to [email protected]: Bug#357400; Package postgresql-common. I'm guessingit's a Tiger issue but I don't know what to do about it.That said, shouldn't/usr/local/pgsql//.psql_historybe/usr/local/pgsql/.psql_historyinstead?

There's no difference (semantically) between the two... http://strobelfilms.com/could-not/could-not-save-history-to-file.html Looking at another machine running unstable and postgresql 7.4, it has both directories /var/lib/postgres/ and /var/lib/postgresql/. Setting up libpgsql-ruby (0.8.0-1.1) ... If both paths are on the same partition, then the cluster should have been moved to the new path. > > > [email protected]:/$ ls /var/lib/post* -d > > > /var/lib/postgrsql >

Browse other questions tagged database postgresql ubuntu-14.04 postgresql-9.3 or ask your own question. Acknowledgement sent to "Jon Webster" : New Bug report received and forwarded. If /var/lib/postgres is a separate partition (or, more precisely, on a different partition than /var/lib/postgresql), then the upgrade will not move the installation, since the dedicated partition should be kept. Source You may have to register before you can post: click the register link above to proceed.

y Get:1 Index of / revolution/main libpgsql-ruby 0.8.0-1.1 [8,166B] Get:2 http://32.repository.backtrack-linux.org/ revolution/main libpgsql-ruby1.8 0.8.0-1.1 [30.2kB] Fetched 38.3kB in 1s (29.1kB/s) Selecting previously deselected package libpgsql-ruby1.8. (Reading database ... 224682 files and Need to get 38.3kB of archives. Acknowledgement sent to "Jon Webster" : Extra info received and forwarded to list.

I got rid of the error message by changing the source to ignore the return code...

sh-4.1$ createuser root -P could not change directory to "/root" Enter password for new role: Enter it again: Shall the new role be a superuser? (y/n) n Shall the new role bye and good luck! 08-15-2011,03:58 AM #3 surajkumarrajpurohit View Profile View Forum Posts Just burned his ISO Join Date Aug 2011 Posts 3 Re: Problem with connecting database thank q zimmaro. Thanks for the tip on there being no real difference in the two paths (i.e., I'm not a Unix guy). Bug reassigned from package `postgresql' to `postgresql'.

Message #43 received at [email protected] (full text, mbox, reply): From: Martin Pitt To: [email protected] Subject: Closing Date: Sun, 16 Apr 2006 20:43:53 +0200 Version: 7.5.18 Hi, since fiddling with the What's New? share|improve this answer answered Jan 7 at 16:19 charlwillia6 112 add a comment| Your Answer draft saved draft discarded Sign up or log in Sign up using Google Sign up have a peek here So, in closing, we've concluded this home directory problem is caused by not upgrading postgresql/stable to postgresql/unstable before installing postgresql-8.1.

Is every parallelogram a rectangle ?? Ooops! Unpacking libpgsql-ruby (from .../libpgsql-ruby_0.8.0-1.1_all.deb) ... Acknowledgement sent to "Jon Webster" : Extra info received and forwarded to list.

So, well, I don't really consider that a bug now, do you? postgres=# select 1; ?column? ---------- 1 (1 row) postgres=# \q could not save history to file "/var/lib/postgresql/.psql_history": No such file or directory postgres(at)vagrant-ubuntu-trusty-64:~$ ls -l /var/lib/postgresql/.psql_history -rw------- 1 postgres postgres 10 Done Building dependency tree Reading state information... Do you have an > > idea how this directory could have been misnamed? > > > > The most likely place is postgresql/sarge.

That is, unless you connect to PSQL using your own account and you continue to get a similar error message. Full text and rfc822 format available. Help, my office wants infinite branch merges as policy; what other options do we have? Then recompile and reinstallPostgreSQL.

its working...... Full text and rfc822 format available. Is the form "double Dutch" still used? Message #20 received at [email protected] (full text, mbox, reply): From: Martin Pitt To: Jon Webster Cc: [email protected] Subject: Re: Bug#357400: Asterisk bugs Date: Sat, 18 Mar 2006 14:19:46 +0100

Notification sent to "Jon Webster" : Bug acknowledged by developer. drwxr-xr-x 41 root root 4096 Jun 26 14:54 .. Johnson wrote:Greetings.Any ideas on how to resolve this problem: test=# \qcould not save history to file "/usr/local/pgsql//.psql_history": PermissiondeniedI don't know about the platform, but shouldn't that refer to your homedirectory?Other installations Nope, I just checked.

If both paths are on the same partition, then the cluster should > have been moved to the new path.