From: | "Ross J(dot) Reedstrom" <reedstrm(at)rice(dot)edu> |
---|---|
To: | pgsql-patches(at)postgresql(dot)org |
Cc: | Patrick Welche <prlw1(at)newn(dot)cam(dot)ac(dot)uk>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Subject: | Re: [HACKERS] psql and readline |
Date: | 2003-02-16 02:29:12 |
Message-ID: | 20030216022912.GC23384@wallace.ece.rice.edu |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-patches |
Here's the patch I promised over on HACKERS - it alters the implementation
of '\e' history tracking for systems that have a readline compatability
library without replace_history_entry. I fall back to pushing the query
onto the history stack after the \e, rather than replacing it.
The patch adds one more place to look for readline headers, and a test
for replace_history_entry. I've only included the patch for configure.in -
I presume configure in CVS is generated on the central server? (I've got
autoconf 2.54 installed, the file in CVS was generated by 2.53 - there are
a number of diffs other than those caused by my additions to configure.in)
Patrick, does this patch work for you, in your build environment?
Ross
Attachment | Content-Type | Size |
---|---|---|
editline.diff | text/plain | 4.0 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2003-02-16 02:33:45 | Re: Evaluate arguments of COALESCE and NULLIF only once. |
Previous Message | Rod Taylor | 2003-02-16 00:50:46 | Object (Domain) locking |