| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | cjthmp(at)gmail(dot)com |
| Cc: | "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: BUG #14031: Failed to Write to History File |
| Date: | 2016-03-18 20:57:48 |
| Message-ID: | CAKFQuwYPydK1s3th1XwQGm97CSEk1o6AXgoTo8Q9UxVOrBKNMA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Thu, Mar 17, 2016 at 8:50 PM, <cjthmp(at)gmail(dot)com> wrote:
> The following bug has been logged on the website:
>
> Bug reference: 14031
> Logged by: cj
> Email address: cjthmp(at)gmail(dot)com
> PostgreSQL version: 9.5.1
> Operating system: Mac
> Description:
>
> I re-installed PostgreSQL 9.5 on my Mac, and now every time I run a query I
> get a "Failed to write to history file". Error. What history file is it
> talking about? How can I fix this?
>
> I've seen this question before, but not an answer. Thanks.
>
Not much help but the history file comes either from "readline" or
"libedit" - those are the two potential O/S provided libraries that psql
uses to make using its command line interface much friendlier.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ilya Matveychikov | 2016-03-18 21:52:36 | Re: Incorrect accounting (n_tup_ins) of non-inserted rows |
| Previous Message | Bronislav.Houdek | 2016-03-18 14:09:37 | BUG #14034: Select for update with inner select doesn't return value after committing by other transaction. |